| 1 |
Opening of the meeting |
|
| R2-2407824 |
(reserved) |
Sergio's tdocs |
| R2-2407825 |
(reserved) |
Sergio's tdocs |
| 2.1 |
Approval of the agenda |
|
| R2-2406201 |
Agenda for RAN2#127 |
Chairman |
| 2.2 |
Approval of the report of the previous meeting |
|
| R2-2406202 |
RAN2#126 Meeting Report |
MCC |
| 2.5 |
Others |
|
| R2-2406203 |
RAN2 Handbook |
MCC |
| R2-2406464 |
Report on RAN2 Cricket team to take on RAN4 |
Offline Rapporteur (ZTE) |
| R2-2407836 |
Update of stage 2 positioning information |
R3 (Nokia, CATT, Ericsson, Huawei, Samsung, Xiaomi, ZTE) |
| R2-2407837 |
Correction on CPA failure states and detection mechanism in stage 2 |
R3 (Nokia, CATT, CMCC, Qualcomm Incorporated, Huawei, ZTE Corporation, Lenovo) |
| R2-2407838 |
Correction on SPR retrieval and forwarding |
R3 (Samsung, Lenovo, Cybercore, Qualcomm, Nokia, Ericsson, Huawei, ZTE, CATT) |
| R2-2407839 |
Correction on Complete Candidate Configuration |
R3 (Huawei, Ericsson, LG Electronics, Samsung) |
| R2-2407840 |
Missing procedure description for pre-configured SRS activation |
R3 (Qualcomm Incorporated, Ericsson, Nokia, Xiaomi, Huawei, CATT) |
| R2-2407841 |
Correction on MIMO with 2TAs in LTM |
R3 (Huawei, China Unicom, CMCC, Nokia, LG Electronics, CATT, Ericsson) |
| R2-2407842 |
Further miscellaneous corrections to QMC procedure |
R3 (Huawei, China Unicom, Lenovo, Ericsson, Nokia, Samsung, ZTE) |
| R2-2407867 |
Further miscellaneous corrections to QMC procedure |
R3 (Huawei, China Unicom, Lenovo, Ericsson, Nokia, Samsung, ZTE) |
| 3 |
Incoming liaisons |
|
| R2-2406204 |
LS on RAN4 vs RAN2 Cricket Match (R4-2410764; contact: Nokia) |
RAN4 |
| R2-2406234 |
LS on Avoiding Cross-TSG TEI (RP-241686; contact: NEC) |
RAN |
| 4.1 |
EUTRA corrections Rel-17 and earlier |
|
| R2-2406272 |
Correction on the field of scg-State |
Huawei, HiSilicon, Qualcomm Incorporated |
| R2-2406273 |
Correction on the field of scg-State |
Huawei, HiSilicon, Qualcomm Incorporated |
| R2-2406274 |
Correction on the field of scg-State |
Huawei, HiSilicon, Qualcomm Incorporated |
| R2-2406275 |
Correction on the field of scg-State |
Huawei, HiSilicon, Qualcomm Incorporated |
| R2-2406631 |
extendedWaitTime correction |
Peraton Labs, CISA ECD, AT&T, Verizon |
| R2-2406646 |
Correction to MIB-MBMS systemFrameNumber field description |
Qualcomm Incorporated, Samsung, ABS, SJTU |
| R2-2406647 |
Correction to MIB-MBMS systemFrameNumber field description |
Qualcomm Incorporated, Samsung, ABS, SJTU |
| R2-2406648 |
Correction to MIB-MBMS systemFrameNumber field description |
Qualcomm Incorporated, Samsung, ABS, SJTU |
| R2-2406649 |
Correction to MIB-MBMS systemFrameNumber field description |
Qualcomm Incorporated, Samsung, ABS, SJTU |
| R2-2406650 |
Correction to MIB-MBMS systemFrameNumber field description |
Qualcomm Incorporated, Samsung, ABS, SJTU |
| R2-2407210 |
Correction to MIB-MBMS systemFrameNumber field description |
Qualcomm Incorporated, Samsung, ABS, SJTU |
| R2-2407632 |
Correction to MIB-MBMS systemFrameNumber field description |
Qualcomm Incorporated, Samsung, ABS, SJTU, Ericsson |
| R2-2407796 |
Correction to MIB-MBMS systemFrameNumber field description |
Qualcomm Incorporated, Samsung, ABS, SJTU, Ericsson |
| R2-2407797 |
Correction to MIB-MBMS systemFrameNumber field description |
Qualcomm Incorporated, Samsung, ABS, SJTU, Ericsson |
| R2-2407798 |
Correction to MIB-MBMS systemFrameNumber field description |
Qualcomm Incorporated, Samsung, ABS, SJTU, Ericsson |
| R2-2407799 |
Correction to MIB-MBMS systemFrameNumber field description |
Qualcomm Incorporated, Samsung, ABS, SJTU, Ericsson |
| 4.3 |
Positioning corrections Rel-16 and earlier |
|
| R2-2406288 |
Correction on SBAS and GNSS ID for posSIB-r15 |
Huawei, HiSIlicon |
| R2-2406289 |
Correction on SBAS and GNSS ID for posSIB-r16 |
Huawei, HiSIlicon |
| R2-2406290 |
Correction on SBAS and GNSS ID for posSIB-r17 |
Huawei, HiSIlicon |
| R2-2406291 |
Correction on SBAS and GNSS ID for posSIB-r18 |
Huawei, HiSIlicon |
| 5.1.1 |
Stage 2 and Organisational |
|
| R2-2406634 |
Alignment of mps-PriorityAccess cause in RRC resume |
Peraton Labs, CISA ECD, Verizon |
| R2-2407281 |
Correction on Transport Channels |
Philips International B.V. |
| R2-2407282 |
Correction on Transport Channels |
Philips International B.V. |
| R2-2407284 |
Correction on Transport Channels |
Philips International B.V. |
| R2-2407288 |
Correction on Transport Channels |
Philips International B.V. |
| R2-2407633 |
Alignment of mps-PriorityAccess cause in RRC resume |
Peraton Labs, CISA ECD, Verizon |
| R2-2407634 |
Correction on Transport Channels |
Philips International B.V. |
| R2-2407775 |
Alignment of mps-PriorityAccess cause in RRC Resume |
Peraton Labs, CISA ECD, Verizon |
| R2-2407776 |
Alignment of mps-PriorityAccess cause in RRC Resume |
Peraton Labs, CISA ECD, Verizon |
| R2-2407777 |
Alignment of mps-PriorityAccess cause in RRC Resume |
Peraton Labs, CISA ECD, Verizon |
| 5.1.2.1 |
MAC |
|
| R2-2407431 |
Clarification on Rel-16 BFR and Rel-17 BFR |
ZTE Corporation |
| 5.1.3.1 |
NR RRC |
|
| R2-2406336 |
Preconditions for MCG reconfiguration with sync |
MediaTek Inc. |
| R2-2406350 |
Correction on the way to include ReconfigurationWithSync in masterCellGroup in RRCReconfiguration |
NTTDOCOMO, INC., Nokia, Nokia Shanghai Bell, Ericsson, Samsung |
| R2-2406351 |
Correction on the way to include ReconfigurationWithSync in masterCellGroup in RRCReconfiguration |
NTTDOCOMO, INC., Nokia, Nokia Shanghai Bell, Ericsson, Samsung |
| R2-2406353 |
Correction on the way to include ReconfigurationWithSync in masterCellGroup in RRCReconfiguration |
NTTDOCOMO, INC., Nokia, Nokia Shanghai Bell, Ericsson, Samsung |
| R2-2406354 |
Correction on the way to include ReconfigurationWithSync in masterCellGroup in RRCReconfiguration |
NTTDOCOMO, INC., Nokia, Nokia Shanghai Bell, Ericsson, Samsung |
| R2-2406799 |
Discussion on going to IDLE triggered by inter-RAT cell selecton or reselection |
vivo |
| R2-2406800 |
Correction on going to IDLE triggered by inter-RAT cell selection or reselection |
vivo |
| R2-2406801 |
Correction on going to IDLE triggered by inter-RAT cell selection |
vivo |
| R2-2406841 |
Correction on IE SRS-CarrierSwitching |
CATT |
| R2-2406842 |
Correction on IE SRS-CarrierSwitching |
CATT |
| R2-2406843 |
Correction on IE SRS-CarrierSwitching |
CATT |
| R2-2406844 |
Correction on IE SRS-CarrierSwitching |
CATT |
| R2-2407083 |
Generic procedure text for SetupRelease |
Ericsson |
| R2-2407084 |
Generic procedure text for SetupRelease |
Ericsson |
| R2-2407085 |
Generic procedure text for SetupRelease |
Ericsson |
| R2-2407086 |
Generic procedure text for SetupRelease |
Ericsson |
| R2-2407636 |
Correction to Parallel Tx capabilities |
Ericsson, Qualcomm Incorporated |
| R2-2407794 |
Correction to Parallel Tx capabilities |
Ericsson, Qualcomm Incorporated |
| R2-2407795 |
Correction to Parallel Tx capabilities |
Ericsson, Qualcomm Incorporated |
| 5.1.3.2 |
UE capabilities |
|
| R2-2407069 |
Parallel Tx capability discussion |
Ericsson, Qualcomm Incorporated |
| R2-2407297 |
Clarification on increasedNumberofCSIRSPerMO |
Huawei, HiSilicon, vivo, MediaTek Inc., Nokia, Nokia Shanghai Bell, ZTE Corporation |
| R2-2407298 |
Clarification on increasedNumberofCSIRSPerMO |
Huawei, HiSilicon, vivo, MediaTek Inc., Nokia, Nokia Shanghai Bell, ZTE Corporation |
| R2-2407299 |
Clarification on increasedNumberofCSIRSPerMO |
Huawei, HiSilicon, vivo, MediaTek Inc., Nokia, Nokia Shanghai Bell, ZTE Corporation |
| R2-2407323 |
Clarification on the Prerequisite of the ssb-AndCSI-RS-RLM (r15) |
ZTE Corporation, Sanechips |
| R2-2407324 |
Clarification on the Prerequisite of the ssb-AndCSI-RS-RLM (r16) |
ZTE Corporation, Sanechips |
| R2-2407325 |
Clarification on the Prerequisite of the ssb-AndCSI-RS-RLM (r17) |
ZTE Corporation, Sanechips |
| R2-2407326 |
Clarification on the Prerequisite of the ssb-AndCSI-RS-RLM (r18) |
ZTE Corporation, Sanechips |
| R2-2407635 |
Correction to Parallel Tx capabilities |
Ericsson, Qualcomm Incorporated |
| R2-2407637 |
Clarification on increasedNumberofCSIRSPerMO |
Huawei, HiSilicon, vivo, MediaTek Inc., Nokia, Nokia Shanghai Bell, ZTE Corporation |
| R2-2407638 |
Clarification on increasedNumberofCSIRSPerMO |
Huawei, HiSilicon, vivo, MediaTek Inc., Nokia, Nokia Shanghai Bell, ZTE Corporation |
| R2-2407639 |
Clarification on increasedNumberofCSIRSPerMO |
Huawei, HiSilicon, vivo, MediaTek Inc., Nokia, Nokia Shanghai Bell, ZTE Corporation |
| R2-2407855 |
Correction to Parallel Tx capabilities |
Ericsson, Qualcomm Incorporated |
| R2-2407856 |
Correction to Parallel Tx capabilities |
Ericsson, Qualcomm Incorporated |
| R2-2407857 |
Correction to Parallel Tx capabilities |
Ericsson, Qualcomm Incorporated |
| R2-2407858 |
Correction to Parallel Tx capabilities |
Ericsson, Qualcomm Incorporated |
| 5.1.3.3 |
Other |
|
| R2-2407341 |
Correction to Relaxed measurement |
LG Electronics |
| R2-2407361 |
Correction to Relaxed measurement |
LG Electronics |
| R2-2407363 |
Correction to Relaxed measurement |
LG Electronics |
| 5.2 |
NR V2X |
|
| R2-2406699 |
Correction to MAC on cast type |
ZTE Corporation, Sanechips |
| R2-2407464 |
MAC correction on resource selection |
LG Electronics Inc. |
| R2-2407472 |
MAC correction on resource selection |
LG Electronics Inc. |
| R2-2407475 |
MAC correction on resource selection |
LG Electronics Inc. |
| R2-2407588 |
MAC correction on resource selection |
LG |
| R2-2407589 |
MAC correction on resource selection |
LG |
| R2-2407590 |
MAC correction on resource selection |
LG |
| 5.3 |
NR Positioning Support |
|
| R2-2406295 |
Correction on SP positioning SRS MAC CE |
Huawei, HiSIlicon |
| R2-2406296 |
Correction on SP positioning SRS MAC CE |
Huawei, HiSIlicon |
| R2-2406297 |
Correction on SP positioning SRS MAC CE |
Huawei, HiSIlicon |
| 6.1.2 |
User Plane corrections |
|
| R2-2406910 |
Discussion on PHR for mTRP PUSCH repetition |
LG Electronics Inc. |
| R2-2406911 |
Correction on PHR for mTRP PUSCH repetition |
LG Electronics. |
| R2-2406912 |
Correction on PHR for mTRP PUSCH repetition (R18) |
LG Electronics Inc. |
| R2-2407137 |
Correction on HARQ process |
Samsung |
| R2-2407138 |
Correction on HARQ process |
Samsung |
| R2-2407171 |
Correction on use of recommended of IAB-MT beam indication. |
Ericsson |
| R2-2407172 |
Correction on use of recommended of IAB-MT beam indication. |
Ericsson |
| R2-2407425 |
Clarification on the activated TCI codepoints for Unified TCI States Activation/Deactivation MAC CE |
Samsung |
| R2-2407426 |
Clarification on the activated TCI codepoints for Unified TCI States Activation/Deactivation MAC CE |
Samsung |
| R2-2407432 |
Clarification On PHR and PHR MAC CE for mTRP |
ZTE Corporation, Samsung, Nokia, CATT, Apple |
| R2-2407564 |
Discussion on PHR for mTRP PUSCH repetition |
LG Electronics Inc., Ericsson |
| R2-2407565 |
Correction on PHR for mTRP PUSCH repetition |
LG Electronics Inc., Ericsson |
| R2-2407566 |
Correction on PHR for mTRP PUSCH repetition |
LG Electronics Inc., Ericsson. |
| R2-2407767 |
Report of [AT127][006][R17 UP] PHR for mTRP (LG, ZTE) |
LG Electronics Inc., ZTE |
| R2-2407768 |
Correction on PHR for mTRP PUSCH repetition (R17) |
LG Electronics Inc., Ericsson, ZTE |
| R2-2407782 |
Correction on PHR for mTRP PUSCH repetition (R17) |
ZTE, LG Electronics Inc., Ericsson, Samsung, CATT, Nokia, Apple |
| 6.1.3.1 |
NR RRC |
|
| R2-2406225 |
LS on inconsistent issue between extended k1 range and RRC parameter DL-DataToUL-ACK-v1700 for R17 NTN (R4-2409974; contact: CMCC) |
RAN4 |
| R2-2406372 |
Corrections on the application of intraFreqReselection |
Huawei, HiSilicon |
| R2-2406373 |
Corrections on the application of intraFreqReselection |
Huawei, HiSilicon |
| R2-2406411 |
Consideration on overlapping preamble range and empty FeatureCombination |
ZTE Corporation |
| R2-2406467 |
Clarification on Validity Duration |
vivo, Ericsson |
| R2-2406468 |
Clarification on Validity Duration |
vivo, Ericsson |
| R2-2406691 |
Correction on Slicing based RACH |
Apple |
| R2-2406692 |
Correction on Slicing based RACH |
Apple |
| R2-2406838 |
Discussion on missing PRACH SCS configuration |
CATT |
| R2-2406839 |
Correction on the missing PRACH SCS configuration |
CATT |
| R2-2406840 |
Correction on the missing PRACH SCS configuration |
CATT |
| R2-2406845 |
On the Inconsistency between extended k1 range and DL-DataToUL-ACK-v1700 (RAN4 LS) |
Nokia |
| R2-2406862 |
Discussion on the inconsistency issue in RAN4 LS R2-2406225 for Rel-17 NR NTN |
CATT |
| R2-2406927 |
Correction for CFRA configuration due to PRACH partitioning |
Huawei, HiSilicon |
| R2-2406928 |
Correction for CFRA configuration due to PRACH partitioning |
Huawei, HiSilicon |
| R2-2406990 |
Miscellaneous corrections to mobility history information |
ZTE Corporation, Sanechips |
| R2-2406991 |
Miscellaneous corrections to mobility history information |
ZTE Corporation, Sanechips |
| R2-2407009 |
Correction on featureCombination and SI-RequestConfig |
ZTE Corporation |
| R2-2407010 |
Correction on featureCombination and SI-RequestConfig |
ZTE Corporation |
| R2-2407080 |
Miscellaneous non-controversial corrections Set XXII |
Ericsson |
| R2-2407081 |
Miscellaneous non-controversial corrections Set XXII |
Ericsson |
| R2-2407082 |
Miscellaneous non-controversial corrections Set XXII |
Ericsson |
| R2-2407089 |
Improvement of procedure text for QoE measurements |
Ericsson |
| R2-2407114 |
Correction of reestablishmentCellId |
Nokia |
| R2-2407115 |
Correction of reestablishmentCellId |
Nokia |
| R2-2407144 |
Clarification on MBS broadcast acquisition |
Samsung, CATT, Nokia, LG Electronics Inc., Ericsson, Apple, Qualcomm Incorporated |
| R2-2407150 |
Clarification on MBS broadcast acquisition |
Samsung, CATT, Nokia, LG Electronics Inc., Ericsson, Apple, Qualcomm Incorporated |
| R2-2407173 |
Correction on when featureCombination is empty |
Ericsson |
| R2-2407174 |
Correction on when featureCombination is empty |
Ericsson |
| R2-2407300 |
Clarification on smtc4list-r17 |
Huawei, HiSilicon |
| R2-2407301 |
Clarification on smtc4list-r17 |
Huawei, HiSilicon |
| R2-2407340 |
Corrections for RA resource related parameters in RA report |
Sharp |
| R2-2407371 |
Clarification on the case the SIB17 is absent |
Google |
| R2-2407428 |
Discussion on indication of reserved SN-side NR-DC and aggregated BW resources |
Nokia |
| R2-2407429 |
Correction to indication of reserved SN-side NR-DC and aggregated BW resources |
Nokia |
| R2-2407430 |
Correction to indication of reserved SN-side NR-DC and aggregated BW resources |
Nokia |
| R2-2407459 |
Clarification on configuring RACH partition in RedCap-specific initial BWP for Msg1-based SI request |
LG Electronics Inc. |
| R2-2407500 |
Correction on mappingPattern for mTRP DG/CG PUSCH repetition schemes |
Nokia |
| R2-2407519 |
Miscellaneous non-controversial corrections Set XXII |
Ericsson |
| R2-2407528 |
Clarification on parallel lists in MeasObjectNR |
Samsung |
| R2-2407529 |
Clarification on parallel lists in MeasObjectNR |
Samsung |
| R2-2407556 |
Correction on power control parameters to support unified TCI state framework |
Ericsson |
| R2-2407557 |
Correction on power control parameters to support unified TCI state framework |
Ericsson |
| R2-2407631 |
[DRAFT] LS on power control parameters for unified TCI state framework |
Ericsson |
| R2-2407642 |
Correction on featureCombination and SI-RequestConfig |
ZTE Corporation, Ericsson, LG Electronics Inc. |
| R2-2407643 |
Correction on featureCombination and SI-RequestConfig |
ZTE Corporation, Ericsson, LG Electronics Inc. |
| R2-2407644 |
Clarification on MBS broadcast acquisition |
Samsung, CATT, Nokia, LG Electronics Inc., Ericsson, Apple, Qualcomm Incorporated |
| R2-2407645 |
Clarification on MBS broadcast acquisition |
Samsung, CATT, Nokia, LG Electronics Inc., Ericsson, Apple, Qualcomm Incorporated |
| R2-2407648 |
Correction to indication of reserved SN-side NR-DC and aggregated BW resources |
Nokia |
| R2-2407649 |
Correction to indication of reserved SN-side NR-DC and aggregated BW resources |
Nokia |
| R2-2407650 |
Miscellaneous non-controversial corrections Set XXII |
Ericsson |
| R2-2407651 |
Miscellaneous non-controversial corrections Set XXII |
Ericsson |
| R2-2407652 |
Miscellaneous non-controversial corrections Set XXII |
Ericsson |
| R2-2407655 |
LS on power control parameters for unified TCI state framework |
RAN2 |
| R2-2407657 |
Miscellaneous corrections on mobility history information |
ZTE Corporation, Sanechips |
| R2-2407658 |
Miscellaneous corrections on mobility history information |
ZTE Corporation, Sanechips |
| R2-2407659 |
Correction on power control parameters to support unified TCI state framework |
Ericsson |
| R2-2407660 |
Correction on power control parameters to support unified TCI state framework |
Ericsson |
| R2-2407661 |
Clarification on Validity Duration |
vivo, Ericsson |
| R2-2407662 |
Clarification on Validity Duration |
vivo, Ericsson |
| R2-2407665 |
Correction on the missing PRACH SCS configuration |
CATT |
| R2-2407666 |
Correction on the missing PRACH SCS configuration |
CATT |
| R2-2407879 |
Correction on featureCombination and SI-RequestConfig |
ZTE Corporation, Ericsson, LG Electronics Inc. |
| R2-2407880 |
Correction on featureCombination and SI-RequestConfig |
ZTE Corporation, Ericsson, LG Electronics Inc. |
| 6.1.3.2 |
UE capabilities |
|
| R2-2406817 |
Corrections to UE capabilities related to Rel-17 URLLC and RedCap |
Huawei, HiSilicon |
| R2-2407076 |
Support of Enhanced channel raster by (e)RedCap UE Rel-17 |
Ericsson |
| R2-2407653 |
Corrections to UE capabilities related to Rel-17 URLLC and RedCap |
Huawei, HiSilicon |
| R2-2407654 |
Corrections to UE capabilities related to Rel-17 URLLC and RedCap |
Huawei, HiSilicon |
| R2-2407826 |
LS on mandated support of the enhanced channel raster by RedCap UEs from Rel-17 (R4-2414409; contact: Ericsson) |
RAN4 |
| R2-2407834 |
Mandatory support of Enhanced channel raster by RedCap UE |
Ericsson |
| R2-2407835 |
Mandatory support of Enhanced channel raster by RedCap UE |
Ericsson |
| 6.2 |
NR Sidelink relay |
|
| R2-2406948 |
Correction on T300 and T302 handling due to relay selection or cell selection |
Huawei, HiSilicon |
| R2-2406949 |
Correction on T300 and T302 handling due to relay selection or cell selection |
Huawei, HiSilicon |
| R2-2407270 |
RRC correction on NR SL U2N Relay UE selection and reselection procedure |
Philips International B.V., NEC |
| R2-2407272 |
RRC correction on NR SL U2N Relay UE selection and reselection procedure |
Philips International B.V., NEC |
| R2-2407495 |
Corrections for SL relay measurements |
ZTE Corporation, Sanechips, Apple, OPPO, Nokia |
| R2-2407496 |
Corrections for SL relay measurements |
ZTE Corporation, Sanechips, Apple, OPPO, Nokia |
| R2-2407724 |
Correction on T300 and T302 handling due to relay selection or cell selection |
Huawei, HiSilicon |
| R2-2407725 |
Correction on T300 and T302 handling due to relay selection or cell selection |
Huawei, HiSilicon |
| R2-2407726 |
RRC correction on NR SL U2N Relay UE selection and reselection procedure |
Philips International B.V., NEC |
| R2-2407727 |
RRC correction on NR SL U2N Relay UE selection and reselection procedure |
Philips International B.V., NEC |
| R2-2407728 |
Corrections for SL relay measurements |
ZTE Corporation, Sanechips, Apple, OPPO, Nokia, Huawei, HiSilicon |
| R2-2407729 |
Corrections for SL relay measurements |
ZTE Corporation, Sanechips, Apple, OPPO, Nokia, Huawei, HiSilicon |
| R2-2407754 |
Corrections for SL relay measurements |
ZTE Corporation, Sanechips, Apple, OPPO, Nokia, Huawei, HiSilicon |
| 6.4 |
NR positioning enhancements |
|
| R2-2406298 |
Correction on PPW for MAC spec |
Huawei, HiSIlicon |
| R2-2406299 |
Correction on PPW for MAC spec |
Huawei, HiSIlicon |
| R2-2406788 |
Correction on SP SRS activation/deactivation MAC CE |
ZTE Corporation, Ericsson |
| R2-2406789 |
Correction on SP SRS activation/deactivation MAC CE |
ZTE Corporation, Ericsson |
| R2-2406790 |
Discussion on DL MAC CE in Rel-17 and Rel-18 SP SRS in RRC_INACTIVE |
ZTE Corporation, Ericsson |
| R2-2407223 |
Corrections related to additional path reporting and QCL for positioning |
Ericsson |
| R2-2407226 |
Corrections related to additional path reporting and QCL for positioning |
Ericsson |
| R2-2407716 |
Correction on SP SRS activation/deactivation MAC CE |
ZTE Corporation, Ericsson |
| R2-2407717 |
Correction on SP SRS activation/deactivation MAC CE |
ZTE Corporation, Ericsson |
| 6.6 |
NR Sidelink enhancements |
|
| R2-2406262 |
Correction on resource (re)selection for IUC |
OPPO |
| R2-2406263 |
Correction on resource (re)selection for IUC |
OPPO |
| R2-2406514 |
Correction on prioritization between SL transmission and MAC CE-triggered SR |
ASUSTeK |
| R2-2406515 |
Correction on prioritization between SL transmission and MAC CE-triggered SR |
ASUSTeK |
| R2-2407011 |
Correction on SL IUC and SL DRX configurations for SL enhancements |
Huawei, HiSilicon |
| R2-2407012 |
Correction on SL IUC and SL DRX configurations for SL enhancements |
Huawei, HiSilicon |
| R2-2407019 |
Correction to MAC on HARQ feedback indicator |
Ericsson |
| R2-2407020 |
Correction to MAC on cast type |
Ericsson |
| R2-2407246 |
Correction to MAC on HARQ feedback indicator |
Ericsson |
| R2-2407405 |
Correction on resource selection for IUC |
LG Electronics Inc. |
| R2-2407412 |
Correction on resource selection for IUC |
LG Electronics Inc. |
| R2-2407591 |
LS on IUC Scheme-2 and Random Selection |
RAN2 |
| R2-2407592 |
Correction to MAC on HARQ feedback indicator |
Ericsson |
| R2-2407593 |
Correction to MAC on HARQ feedback indicator |
Ericsson |
| 7.0.1 |
UE Capabilities |
|
| R2-2406210 |
LS on Rel-18 RAN1 UE features list for NR after RAN1#117 (R1-2405566; contact: NTT DOCOMO, AT&T) |
RAN1 |
| R2-2406232 |
LS on RAN4 UE feature list for Rel-18 (version 5) (R4-2410748; contact: CMCC) |
RAN4 |
| R2-2406535 |
Correction to UE capabilities and configuration |
Google |
| R2-2407327 |
Consideration on the Redundant Prerequisite of UE Features |
ZTE Corporation, Sanechips |
| R2-2407328 |
Draft LS on the Redundant Prerequisite |
ZTE Corporation, Sanechips |
| R2-2407805 |
Correction to UE capabilities and configuration |
Google |
| R2-2407846 |
Updates and Introduction of UE capabilities for Rel-18 WIs |
Intel Corporation |
| R2-2407847 |
Updates and Introduction of UE capabilities for Rel-18 WIs |
Intel Corporation |
| 7.0.2.1 |
RACH-less HO |
|
| R2-2406300 |
Rapporteur MAC CR for generalized RACH-less HO/LTM [RACH-lessHO] |
Huawei, HiSilicon |
| R2-2406492 |
Correction on retransmission in RACH-less HO |
CATT |
| R2-2406493 |
Correction on RRC parameters for RACH-less LTM cell switch |
CATT |
| R2-2407180 |
Correction on beam indication for NTN RACH-less [RACH-lessHO] |
Ericsson |
| R2-2407181 |
Misc RRC corrections for RACH-less HO [RACH-lessHO] |
Ericsson (Rapportuer) |
| R2-2407787 |
Misc RRC corrections for RACH-less HO [RACH-lessHO] |
Ericsson |
| R2-2407818 |
Rapporteur MAC CR for generalized RACH-less HO/LTM [RACH-lessHO] |
Huawei, HiSilicon |
| 7.0.2.2 |
NR network-controlled repeaters |
|
| R2-2406277 |
Discussion on NCR capability |
Huawei, HiSilicon, Intel Corporation |
| R2-2406278 |
Correction on NCR capability |
Huawei, HiSilicon, Intel Corporation |
| R2-2406279 |
Correction on NCR capability |
Huawei, HiSilicon, Intel Corporation |
| R2-2406415 |
Introduction of waveform capability for NCR-MT |
ZTE Corporation (Rapporteur), Fujitsu |
| R2-2406416 |
Introduction of waveform capability for NCR-MT |
ZTE Corporation (Rapporteur), Fujitsu |
| R2-2407524 |
Introduction of waveform capability for NCR-MT |
ZTE Corporation (Rapporteur), Fujitsu |
| R2-2407525 |
Introduction of waveform capability for NCR-MT |
ZTE Corporation (Rapporteur), Fujitsu |
| R2-2407814 |
[AT127][010][NCR] Capability CRs (ZTE/Huawei) |
ZTE Corporation, Huawei |
| R2-2407819 |
Correction on NCR capability |
Huawei, HiSilicon, Intel Corporation |
| 7.0.2.3 |
NR support for UAV |
|
| R2-2406597 |
Miscellaneous Corrections in 38.331 |
Ericsson |
| R2-2407193 |
Correction for NR UAV capabilities |
Huawei, HiSilicon |
| R2-2407196 |
Correction for UAV capabilities |
Huawei, HiSilicon |
| R2-2407747 |
Correction for UAV capabilities |
Huawei, HiSilicon, Nokia, Qualcomm, Lenovo, Samsung |
| R2-2407784 |
Correction for NR UAV capabilities |
Huawei, HiSilicon |
| 7.0.2.4 |
Mobile Terminated Small Data Transmission |
|
| R2-2406304 |
Rapporteur MAC CR for MT-SDT |
Huawei, HiSIlicon |
| R2-2407580 |
Rapporteur MAC CR for MT-SDT |
Huawei, HiSIlicon |
| 7.0.2.5 |
IDC enhancements for NR and MR-DC |
|
| R2-2406706 |
Miscellaneous corrections for IDC |
Xiaomi |
| R2-2407292 |
Discussion on handling of TDM Config for IDC |
Huawei, HiSilicon |
| 7.0.2.6 |
Mobile IAB (Integrated Access and Backhaul) for NR |
|
| R2-2406330 |
Corrections on mobile IAB terminologies |
Huawei, HiSilicon (Rapporteur) |
| R2-2407170 |
Misc RRC corrections for mobile IAB |
Ericsson (Rapportuer) |
| R2-2407748 |
Corrections on mobile IAB terminologies |
Huawei, HiSilicon (Rapporteur) |
| 7.0.2.7 |
Timing Resiliency and URLLC Enh |
|
| R2-2407476 |
Correction on UE determining the clock quality information update |
Huawei, HiSilicon |
| 7.0.2.8 |
Others |
|
| R2-2406276 |
Correction on NTN |
Huawei, HiSilicon |
| R2-2406338 |
Discussion on supporting eMBS in NTN |
Huawei, HiSilicon |
| R2-2406412 |
Restructure of RACH resource set selection procedure in MAC |
ZTE Corporation |
| R2-2406413 |
Correction on RACH resource set selection--Option 1 |
ZTE Corporation |
| R2-2406414 |
Correction on RACH resource set selection--Option 2 |
ZTE Corporation |
| R2-2406814 |
Corrections on SI request with Msg1 repetition |
Lenovo |
| R2-2406823 |
Correction on multicast DRX to support NTN in RRC_INACTIVE [MBSoverNTN_RRCINACTIVE] |
Nokia, Qualcomm |
| R2-2407031 |
Miscellaneous corrections |
Samsung (Rapporteur), Ericsson |
| R2-2407032 |
Miscellaneous corrections |
Samsung (Rapporteur), Ericsson |
| R2-2407169 |
Correction on absoluteFrequencySSB corresponding to CD-SSB for PCell |
vivo, ZTE |
| R2-2407266 |
Discussion on multicast DRX to support NTN in INACTIVE |
LG Electronics Inc. |
| R2-2407494 |
Discussion on extensions of ToAddModList |
Samsung |
| R2-2407522 |
Correction on RACH resource set selection---Option 1 |
ZTE Corporation |
| R2-2407523 |
Correction on RACH resource set selection--Option 2 |
ZTE Corporation |
| R2-2407569 |
Reply LS on Rel-18 higher-layers parameter list |
RAN2 |
| R2-2407570 |
ASN.1 names in RAN1 parameter list Rev 1 |
Ericsson |
| R2-2407577 |
Miscellaneous corrections |
Samsung (Rapporteur), Ericsson |
| R2-2407578 |
Miscellaneous corrections |
Samsung (Rapporteur), Ericsson |
| R2-2407774 |
Corrections on SI request with Msg1 repetition |
Lenovo, Huawei, HiSilicon, Philips International B.V. |
| R2-2407778 |
Correction on DRX to support eMBS in NTN |
Huawei, HiSilicon, Qualcomm, LG Electronics Inc, vivo, Ericsson, Nokia |
| R2-2407779 |
Correction to support eMBS in NTN |
Huawei, HiSilicon, Qualcomm, LG Electronics Inc, vivo, Ericsson, Nokia |
| R2-2407788 |
Correction on extension of ToAddModList |
Samsung |
| R2-2407813 |
Correction on RACH resource set selection---Option 1 |
ZTE Corporation |
| R2-2407821 |
Correction on RACH resource set selection---Option 1 |
ZTE Corporation |
| R2-2407827 |
Reply LS on Rel-18 higher-layers parameter list |
RAN2 |
| R2-2407828 |
Correction on absoluteFrequencySSB corresponding to CD-SSB for PCell |
vivo, ZTE |
| R2-2407877 |
Correction on RACH resource set selection---Option 1 |
ZTE Corporation |
| 7.2.1 |
Organizational |
|
| R2-2406207 |
LS on the UE role list in RSPP-Metadata (C1-243690; contact: ZTE) |
CT1 |
| R2-2406208 |
Reply LS on SL positioning measurement (R1-2405511; contact: Huawei) |
RAN1 |
| R2-2406213 |
Reply LS on DL-AoD measurements in NR-PRU-DL-Info forwarded to target UE (R1-2405586; contact: Nokia) |
RAN1 |
| R2-2406228 |
LS on synchronization source change at the transmitting anchor UE in SL positioning (R4-2410352; contact: Ericsson) |
RAN4 |
| R2-2406238 |
Reply LS on application layer ID (S2-2407318; contact: Xiaomi) |
SA2 |
| R2-2406292 |
Rapporteur MAC CR for R18 positioning |
Huawei, HiSilicon |
| R2-2406315 |
Rapporteur MAC CR for R18 positioning |
Huawei, HiSIlicon |
| R2-2406791 |
Draft reply LS on the UE role list in RSPP-Metadata |
ZTE Corporation |
| R2-2406950 |
Miscellaneous corrections to LPP specification |
CATT |
| R2-2407228 |
draft LS reply on synchronization source change at the transmitting anchor UE in SL positioning |
Ericsson |
| R2-2407718 |
Reply LS on the UE role list in RSPP-Metadata |
RAN2 |
| R2-2407720 |
Corrections to LPP specification |
CATT, Ericsson, Qualcomm, Nokia |
| R2-2407722 |
Rapporteur MAC CR for R18 positioning |
Huawei, HiSIlicon |
| R2-2407854 |
Rapporteur MAC CR for R18 positioning |
Huawei, HiSilicon |
| 7.2.2 |
Stage 2 |
|
| R2-2406508 |
Corrections on TS 38.305 for time windows configuration |
CATT, Nokia, NSB, Ericsson, Qualcomm Incorporated |
| R2-2407227 |
DRX and PRS alignment for positioning |
Ericsson, Intel Corporation |
| R2-2407234 |
Correction of Notes for Assistance Data Transfer procedures |
Philips International B.V. |
| R2-2407752 |
Correction to LPP Measurement Time Windows and SLPP Assistance Data Transfer procedures |
Qualcomm Incorporated |
| 7.2.3 |
SLPP corrections |
|
| R2-2406294 |
Discussion on the remaining issues for SLPP for R18 POS |
Huawei, HiSilicon |
| R2-2406374 |
[Post126][410] 38.355 update Open Issue list |
Intel Corporation |
| R2-2406375 |
Miscellaneous corrections to SLPP specification |
Intel Corporation |
| R2-2406509 |
Correction on SL-RTT-provideLocationInformation field description in TS 38.355 |
CATT, CICTCI |
| R2-2406516 |
Clarification on RSPP metadata for direct communication request message |
ASUSTeK |
| R2-2406809 |
Miscellaneous corrections on SLPP |
Lenovo |
| R2-2407146 |
Correction to SLPP PDU Common Contents |
Qualcomm Incorporated |
| R2-2407369 |
Correction on SL-RTT-provideLocationInformation field description in TS 38.355 |
CATT, CICTCI |
| R2-2407719 |
Miscellaneous corrections to SLPP specification |
Intel Corporation |
| R2-2407753 |
Miscellaneous corrections to SLPP specification |
Intel Corporation |
| R2-2407872 |
Miscellaneous corrections to SLPP specification |
Intel Corporation |
| 7.2.4 |
LPP corrections |
|
| R2-2407149 |
Editorial clean up of NR-UL-SRS-Capability |
Qualcomm Incorporated |
| R2-2407230 |
Corrections related to carrier phase measurements |
Ericsson |
| R2-2407253 |
On-demand DL-PRS bandwidth aggregation corrections |
Nokia |
| 7.2.5 |
RRC corrections |
|
| R2-2406405 |
Miscellaneous Corrections for sidelink positioning |
vivo |
| R2-2406510 |
Corrections on SL positioning in TS 38.331 |
CATT |
| R2-2406793 |
Correction on SRS transmission in RRC_INACTIVE |
ZTE Corporation |
| R2-2407221 |
Miscellaneous Positioning Corrections |
Ericsson, Philips International, vivo, CATT |
| R2-2407273 |
RRC correction on NR sidelink positioning |
Philips International B.V. |
| R2-2407559 |
Corrections for the extension of these IEs which do not support the maximum number of CBR ranges and levels for sidelink positioning in TS 38.331 |
CATT, Ericsson |
| R2-2407721 |
Miscellaneous Positioning Corrections |
Ericsson |
| R2-2407769 |
Extension of cells in Validity area and correction of SL CBR Range parameters |
Ericsson, CATT, ZTE Corporation |
| R2-2407861 |
Miscellaneous Positioning Corrections |
Ericsson, Philips International B.V., vivo, CATT |
| R2-2407862 |
Extension of cells in Validity area |
Ericsson, CATT, ZTE Corporation |
| R2-2407863 |
Post127][405][POS] Rel-18 positioning RRC CRs (Ericsson) |
Ericsson |
| R2-2407883 |
Miscellaneous Positioning Corrections |
Ericsson, Philips International B.V., vivo, CATT |
| R2-2407884 |
Extension of cells in Validity area |
Ericsson, CATT, ZTE Corporation |
| 7.2.6 |
MAC corrections |
|
| R2-2406293 |
Discussion on the remaining issues for MAC for R18 POS |
Huawei, HiSilicon |
| R2-2406376 |
eLCID for SL-PRS Resource Request MAC CE |
Intel Corporation |
| R2-2406404 |
Correction on UE behavior of SL-PRS transmission |
vivo |
| R2-2406792 |
Correction on SL pos in dedicated pool and SRS aggregation MAC CE in MAC spec |
ZTE Corporation |
| R2-2406855 |
SL-PRS Resource Request MAC CE in the logical channel prioritization list |
Samsung |
| R2-2407232 |
Aggregated Resource Definition and corrections |
Ericsson |
| R2-2407296 |
Corrections on SL-PRS |
ASUSTeK |
| R2-2407723 |
[AT127][405][POS] C field in relation to cell ID and BWP ID in RRC_INACTIVE (ZTE) |
ZTE Corporation |
| R2-2407853 |
LS on CSI-RS/SRS for spatial relation in RRC_INACTIVE |
RAN2 |
| 7.2.7 |
UE capabilities |
|
| R2-2406810 |
Addition of capability sl-PathlossBasedOLPC-SL-RSRP-Report-r18 (FG R1 41-1-17) in UECapabilityInformation message |
Lenovo |
| R2-2407560 |
Corrections on the UE capability of indication on supporting the extension for sidelink positioning in TS 38.331 |
CATT, Ericsson |
| 7.3.1 |
Organizational |
|
| R2-2406603 |
Network energy savings for NR miscellaneous RRC CR |
Huawei, HiSilicon |
| 7.3.2 |
Other |
|
| R2-2406602 |
Discussion on the SFN issues of Cell DTX/DRX |
Huawei, HiSilicon |
| R2-2406668 |
Remaining issue on SFN timing of Cell DTX/DRX |
Apple |
| R2-2406917 |
Clarification for SP CSI reporting on PUCCH |
Samsung |
| R2-2406999 |
Discussion on the clarification of the SFN on Cell DTXDRX |
CATT |
| R2-2407060 |
NW identifying RACH for emergency call |
Nokia, Nokia Shanghai Bell |
| R2-2407070 |
Handling of inter-band SSB-less configuration |
Ericsson |
| R2-2407128 |
Coexistence of Cell DTXDRX and RACH-less LTM |
Rakuten Mobile, Inc |
| R2-2407766 |
Miscellaneous MAC corrections for network energy savings |
InterDigital |
| R2-2407801 |
Miscellaneous MAC corrections for network energy savings |
InterDigital |
| R2-2407881 |
Miscellaneous MAC corrections for network energy savings |
InterDigital |
| 7.4.1 |
Organizational |
|
| R2-2406217 |
Reply LS on intra-SN SCPAC in MN format (R3-243775; contact: ZTE) |
RAN3 |
| R2-2406227 |
Reply LS on LTM L1 intra and inter-frequency measurements (R4-2410303; contact: Ericsson) |
RAN4 |
| 7.4.2 |
Control plane corrections |
|
| R2-2406332 |
Miscellaneous Corrections for SCPAC |
CATT |
| R2-2406337 |
Rel-18 LTM CP remaining issues |
MediaTek Inc. |
| R2-2406355 |
Leftover LTM UE capability issues |
MediaTek Inc. |
| R2-2406417 |
Miscellaneous corrections for mobility enhancements |
ZTE Corporation |
| R2-2406418 |
Inter-node coordination on L1 measurement for LTM |
ZTE Corporation |
| R2-2406438 |
Discussion on the impact of s-Measure on L1 measurement |
vivo |
| R2-2406476 |
Report of [Post126][514][R18MobE] UE capabilities Open Issues (Intel) |
Intel Corporation |
| R2-2406477 |
Draft 331 CR on updates to UE FeMob LTM capabilities |
Intel Corporation |
| R2-2406478 |
Draft 306 CR on updates to UE FeMob LTM capabilities |
Intel Corporation |
| R2-2406531 |
Discussion on remaining issues for SCPAC |
OPPO |
| R2-2406552 |
Triggering LTM Cell Switch without L1 Measurement and Reports |
Google Ireland Limited |
| R2-2406726 |
Clarification on LTM configuration |
Apple |
| R2-2406847 |
Miscellaneous Rel-18 LTM Corrections (Early decoding, TA acquisition and estimation) |
Nokia |
| R2-2406852 |
Discussion on LTM fast processing capabilities |
Google Ireland Limited |
| R2-2407050 |
RRC corrections for Mobility Enhancements |
Samsung |
| R2-2407072 |
correction related to security configuration for SCPAC and corrections on EMR reselection measurement reporting |
Nokia |
| R2-2407091 |
Draft CR for subsequent CPAC corrections |
Ericsson |
| R2-2407175 |
Misc RRC corrections for feMob |
Ericsson (Rapportuer) |
| R2-2407176 |
Remaining issues related to LTM |
Ericsson |
| R2-2407177 |
Summary of RRC proposals for feMob |
Ericsson |
| R2-2407200 |
RRC issues for LTM |
Huawei, HiSilicon |
| R2-2407370 |
Discussion on PRACH occasion validation for LTM |
Qualcomm Incorporated |
| R2-2407410 |
Correction on LTM related procedure for UE-based TA measurement |
Sharp |
| R2-2407449 |
TP for Stage 2 in coexistence case |
Lenovo |
| R2-2407562 |
Discussion on RAN3 LS on intra-SN SCPAC in MN format |
ZTE Corporation |
| R2-2407584 |
Discussion summary on [AT127][104][MOB] |
MediaTek, ZTE |
| R2-2407585 |
Misc RRC corrections for feMob |
Ericsson |
| R2-2407586 |
Miscellaneous corrections for mobility enhancements |
ZTE Corporation |
| R2-2407595 |
[Discussion summary of Post-105] |
Ericsson |
| R2-2407596 |
[Discussion summary of Post-106] |
ZTE Corporation |
| R2-2407599 |
Draft 331 CR on updates to UE FeMob LTM capabilities |
Intel Corporation |
| R2-2407600 |
Draft 306 CR on updates to UE FeMob LTM capabilities |
Intel Corporation |
| R2-2407601 |
LS on LTM L1 intra and inter-frequency measurements capabilities |
RAN2 |
| R2-2407604 |
Miscellaneous corrections for mobility enhancements |
ZTE Corporation, Ericsson |
| R2-2407606 |
L3 measurement based LTM support over F1 |
RAN2 |
| R2-2407770 |
L3 measurement based LTM mobility support over F1 |
Vodafone |
| R2-2407771 |
LS on L3 measurement based LTM mobility support over F1 |
Vodafone |
| R2-2407859 |
Draft 331 CR on updates to UE FeMob LTM capabilities |
Intel Corporation |
| 7.4.3 |
User plane corrections |
|
| R2-2406331 |
Corrections to TS 38.321 for LTM |
CATT |
| R2-2406349 |
MAC corrections for LTM |
Samsung Electronics Co., Ltd |
| R2-2406439 |
Discussion on MAC open issue for LTM |
vivo |
| R2-2406517 |
Discussion on fallback RACH for LTM |
ASUSTeK |
| R2-2406530 |
Discussion on carrier selection for RACH-LESS LTM |
OPPO |
| R2-2406853 |
Corrections of MAC issues for RACH-less LTM |
NEC |
| R2-2407197 |
User plane corrections for LTM |
Huawei, HiSilicon |
| R2-2407198 |
MAC CR rapporteur summary |
Huawei, HiSilicon |
| R2-2407199 |
Issues for RACH-less LTM cell switch |
Huawei, HiSilicon |
| R2-2407433 |
Consideration on Remaining Issues on LTM UP Aspect |
ZTE Corporation |
| R2-2407563 |
User plane corrections for LTM |
Huawei, HiSilicon |
| R2-2407587 |
User plane corrections for LTM |
Huawei, HiSilicon |
| R2-2407597 |
[AT127][108][MOB] MAC CR discussion summary (Huawei) |
Huawei |
| 7.5.1 |
Organizational |
|
| R2-2406925 |
Parameter names corrections for XR |
Huawei, HiSilicon |
| R2-2407789 |
Corrections for XR |
Qualcomm |
| R2-2407811 |
Corrections for XR |
Qualcomm Incorporated, Ericsson |
| R2-2407876 |
Corrections for XR |
Qualcomm Incorporated, Ericsson |
| 7.5.2 |
Control plane corrections |
|
| R2-2407375 |
Non-integer DRX Configuration when UE enters RRC_INACTIVE |
CATT |
| 7.5.3 |
User plane corrections |
|
| R2-2406301 |
Remaining issues for DRX operation for XR |
Huawei, HiSilicon |
| R2-2406394 |
PDCP SN gap report and updating RX_NEXT |
Nokia, Nokia Shanghai Bell |
| R2-2406440 |
Discussion on DRX_SFN_COUNTER initialization for handover case |
vivo |
| R2-2406504 |
Corrections for PDCP SN Gap Reporting |
Samsung |
| R2-2406555 |
Further Consideration on DRX SFN Counter Initialization |
CATT |
| R2-2406598 |
Remaining Open Issues for PDCP SN Gap Reporting |
Ericsson |
| R2-2406607 |
MAC Corrections for Rel-18 XR |
Samsung |
| R2-2406777 |
Discussion on PDCP window update based on the SN gap report |
vivo |
| R2-2406779 |
Further discussion on the DRX_SFN_COUNTER initialization |
OPPO |
| R2-2406805 |
Corrections on DSR MAC CE |
Langbo |
| R2-2406891 |
Update RX_NEXT based on PDCP SN gap report |
Lenovo |
| R2-2406909 |
Initialization of DRX_SFN_COUNTER at handover |
ZTE Corporation, Sanechips |
| R2-2406918 |
Correction to DRX_SFN_COUNTER for handover case |
ZTE Corporation, Sanechips |
| R2-2406926 |
Correction for discarding operation for XR |
Huawei, HiSilicon, Nokia (Rapporteur) |
| R2-2407046 |
Discussion on user plane corrections |
Ericsson |
| R2-2407061 |
Remaining issues for on setting DRX SFN counter during handover |
Nokia, Nokia Shanghai Bell |
| R2-2407579 |
Correction for discarding operation for XR |
Huawei, HiSilicon, Nokia (Rapporteur) |
| 7.6.1 |
Organizational |
|
| R2-2406211 |
LS on Rel-18 RAN1 UE features list for LTE after RAN1#117 (R1-2405569; contact: NTT DOCOMO, AT&T) |
RAN1 |
| R2-2406938 |
Miscellaneous MAC correction for IoT NTN |
MediaTek |
| R2-2407303 |
Miscellaneous corrections to TS 36.331 for IoT NTN |
Huawei, HiSilicon |
| R2-2407615 |
Miscellaneous corrections to TS 36.331 for IoT NTN |
Huawei, HiSilicon |
| R2-2407620 |
Miscellaneous MAC correction for IoT NTN |
MediaTek |
| R2-2407626 |
Correction for IoT NTN neighbour cell measurements and TN to NTN mobility |
Ericsson, Samsung |
| R2-2407627 |
Corrections of UE Capabilities in IoT NTN |
Qualcomm Inc. |
| R2-2407868 |
Correction for IoT NTN neighbour cell measurements and TN to NTN mobility |
Ericsson, Samsung |
| 7.6.2 |
Corrections |
|
| R2-2406329 |
Correction on SIB33 |
CATT |
| R2-2406450 |
Miscellaneous RRC Correction for IoT-NTN |
vivo |
| R2-2406642 |
Clarification of note on UL and DL parallel scheduling for NB-IoT |
Qualcomm Incorporated |
| R2-2406951 |
Discussion on RRC Corrections to IoT NTN |
MediaTek Inc. |
| R2-2407166 |
Further discussion on T390 stop and GNSS validity report during C-DRX inactive time |
Nokia, Nokia Shanghai Bell |
| R2-2407254 |
Various corrections for IoT NTN Rel-18 |
Samsung |
| R2-2407302 |
Clarification on scenario support |
Huawei, HiSilicon |
| R2-2407538 |
GNSS correction for IoT NTN |
ZTE Corporation, Sanechips |
| R2-2407553 |
R18 IoT NTN GNSS extension |
Ericsson |
| R2-2407791 |
RRC Corrections to IoT NTN |
MediaTek Inc. |
| 7.7.1 |
Organizational |
|
| R2-2406215 |
Reply LS on Reference Point for SSB-TimeOffset (R1-2405719; contact: Apple) |
RAN1 |
| R2-2406229 |
Reply LS on reference point for SSB-TimeOffset (R4-2410381; contact: Apple) |
RAN4 |
| R2-2407239 |
Rapporteur Input to Rel-18 NR NTN |
Ericsson |
| R2-2407611 |
Miscellaneous corrections to Rel-18 NR NTN |
Ericsson |
| R2-2407621 |
Stage-2 corrections for NR NTN |
THALES |
| R2-2407624 |
UE Capabilities for dedicated NTN assistance information and for acquiring SIB19 |
Intel Corporation |
| R2-2407625 |
UE Capabilities for dedicated NTN assistance information and for acquiring SIB19 |
Intel Corporation |
| 7.7.2 |
Corrections |
|
| R2-2406280 |
Correction on network verification of UE location |
Huawei, HiSilicon, CATT |
| R2-2406328 |
Discussion on the absence of validity duration in SIB19 broadcast by a TN serving cell |
CATT |
| R2-2406451 |
Remaining Issues on FR2-NTN Support |
vivo |
| R2-2406641 |
Discussion on soft satellite switch with re-sync |
Qualcomm Incorporated |
| R2-2406727 |
Clarification on Reference Point for SSB-TimeOffset |
Apple |
| R2-2406846 |
Addressing Various Release 18 NTN Issues |
Nokia |
| R2-2406992 |
Miscellaneous corrections to epochTime |
ZTE Corporation, Sanechips |
| R2-2407238 |
Remaining open issues for NR NTN enhancements |
Ericsson |
| R2-2407255 |
Miscellaneous corrections to NR NTN Rel-18 |
Samsung |
| R2-2407482 |
Clarification on the ssb-TimeOffset |
Google |
| R2-2407612 |
Report of [AT127][301][R18 NR NTN] corrections for satellite switch with re-sync |
Qualcomm Incorporated |
| R2-2407613 |
Report of [AT127][302][R18 NR NTN] absence of validity duration in SIB19 |
CATT |
| R2-2407614 |
Report of [AT127][303][R18 NR NTN] Stage 2 text for trigger conditions |
OPPO |
| R2-2407628 |
Corrections for PUCCH repetition for Msg4 HARQ-ACK |
InterDigital |
| R2-2407629 |
Correction on network verification of UE location |
Huawei, HiSilicon, CATT |
| R2-2407630 |
LS on correction on network verification of UE location |
RAN2 |
| R2-2407869 |
Correction on network verification of UE location |
Huawei, HiSilicon, CATT |
| R2-2407887 |
LS on correction on network verification of UE location |
RAN2 |
| 7.9.2 |
Stage 2 corrections |
|
| R2-2406698 |
Corrections for U2U relay |
ZTE Corporation, Sanechips |
| R2-2407059 |
draft_(Rel-18)_38.300 relay stage 2 CR_rapp |
LG Electronics France |
| R2-2407267 |
Correction on NR SL Multi-path relay operation |
Philips International B.V. |
| R2-2407756 |
Corrections on NR sidelink relay enhancements |
LG Electronics (Rapporteur) |
| R2-2407772 |
Rel-18 relay stage 2 rapporteur CR |
LG Electronics |
| R2-2407873 |
Corrections on NR sidelink relay enhancements |
LG Electronics (Rapporteur) |
| 7.9.3 |
RRC corrections |
|
| R2-2406368 |
Correction for U2N remote UE's serving cell during path switch |
OPPO |
| R2-2406369 |
Discussion on SLRB index in SUI for L2 U2U relay |
OPPO |
| R2-2406556 |
Clarification on the filtering of SL-RSRP for U2U relay |
CATT |
| R2-2406557 |
Correction on the indirect path failure reporting condition |
CATT |
| R2-2406599 |
Remaining Open Issues in 38.331 |
Ericsson |
| R2-2406679 |
Discussion on remaining RRC issues for NR Sidelink relay enhancements |
Apple |
| R2-2406680 |
Miscellaneous corrections on TS 38.331 |
Apple |
| R2-2406697 |
Corrections for SL relay |
ZTE Corporation, Sanechips |
| R2-2406946 |
Miscellaneous corrections for SL relay enhancements |
Huawei, HiSilicon |
| R2-2407116 |
Correction in U2U relay sidelink DRB addition/modification |
Nokia |
| R2-2407268 |
RRC correction on NR SL U2U relay operation |
Philips International B.V. |
| R2-2407411 |
Discussion on U2U relay related issues |
Sharp |
| R2-2407755 |
Miscellaneous corrections for SL relay enhancements |
Huawei, HiSilicon, OPPO, CATT, Apple, ZTE Corporation, Sanechips, Nokia, Philips International B.V., Sharp |
| R2-2407790 |
Miscellaneous corrections for SL relay enhancements |
Huawei, HiSilicon |
| 7.9.5 |
MAC, RLC, and PDCP corrections |
|
| R2-2406600 |
Remaining Open Issues in 38.323 |
Ericsson |
| R2-2406947 |
Correction on data transmission and data valume calculation in MP |
Huawei, HiSilicon |
| R2-2407293 |
RLC correction for multi-path relay with N3C |
Huawei, HiSilicon |
| R2-2407751 |
RLC correction for multi-path relay with N3C |
Huawei, HiSilicon |
| R2-2407765 |
Correction on data transmission and data volume calculation in MP |
InterDigital, Huawei, HiSilicon |
| 7.9.6 |
UE capabilities |
|
| R2-2407103 |
Discussion on MP relay capabilities |
Qualcomm Incorporated |
| 7.11.1 |
Organizational |
|
| R2-2407477 |
Miscellaneous correction on eMBS |
Huawei, HiSilicon |
| R2-2407736 |
Miscellaneous corrections on eMBS |
Huawei, HiSilicon, CATT, Samsung, Nokia |
| R2-2407750 |
Reply LS on the MBS broadcast service continuity and MBS session identification (S4-241257; contact: Qualcomm) |
SA4 |
| R2-2407860 |
Report of [POST127][505][MBS] RRC CR (Huawei) |
Huawei, HiSilicon |
| 7.11.2 |
Corrections |
|
| R2-2406281 |
Correction on the capabilities on PTM retransmission |
Huawei, HiSilicon, Intel Corporation, Nokia, vivo |
| R2-2406282 |
Correction on the capabilities on PTM retransmission |
Huawei, HiSilicon, Intel Corporation, Nokia, vivo |
| R2-2406333 |
Corrections on UE behavior in Multicast MCCH-Less Cell |
CATT, CBN, China Broadnet |
| R2-2406345 |
Correction on PTM Retransmission Capability |
Samsung |
| R2-2406507 |
Corrections for Multicast Reception |
Samsung |
| R2-2406661 |
Data losing avoiding for multicast reception in RRC_INACTIVE |
Sharp |
| R2-2406953 |
[N103] [N105] Control plane aspects of multicast reception in RRC_INACTIVE state |
Nokia |
| R2-2407395 |
Validity of PTM configuration in RRCRelease |
Ericsson |
| R2-2407474 |
Correction on broadcast reception for eRedcap UE |
Huawei, HiSilicon |
| R2-2407526 |
RedCap UE's Multicast reception in RRC_INACTIVE - not a good idea |
ZTE Corporation, Sanechips |
| R2-2407527 |
Search space configuration for RedCap UE’s MBS broadcast reception |
ZTE Corporation, Sanechips |
| R2-2407737 |
Correction for error data handling for MBS |
Samsung, Apple |
| R2-2407738 |
Summary of [AT127][507][MBS] MBS and MT-SDT co-existence (Sharp) |
Sharp |
| R2-2407809 |
Correction on the capabilities on PTM retransmission [PTM_ReTx_Mcast_HARQ_Disb] |
Huawei, HiSilicon, Intel Corporation, Nokia, vivo, Samsung |
| R2-2407810 |
Correction on the capabilities on PTM retransmission [PTM_ReTx_Mcast_HARQ_Disb] |
Huawei, HiSilicon, Intel Corporation, Nokia, vivo, Samsung |
| R2-2407874 |
Correction on the capabilities on PTM retransmission [PTM_ReTx_Mcast_HARQ_Disb] |
Huawei, HiSilicon, Intel Corporation, Nokia, vivo, Samsung |
| R2-2407875 |
Correction on the capabilities on PTM retransmission [PTM_ReTx_Mcast_HARQ_Disb] |
Huawei, HiSilicon, Intel Corporation, Nokia, vivo, Samsung |
| 7.13.1 |
Organizational |
|
| R2-2406218 |
Reply LS on MDT for NPN (R3-243892; contact: Ericsson) |
RAN3 |
| R2-2406219 |
Reply LS to SA5 on improved KPIs involving end-to-end data volume transfer time analytics (R3-243941; contact: Nokia) |
RAN3 |
| R2-2407117 |
Stage 2 alignments with stage 3 specification |
Nokia, NEC |
| R2-2407338 |
Miscellaneous corrections on R18 SONMDT for 36.331 |
Huawei, HiSilicon |
| 7.13.2 |
Corrections |
|
| R2-2406997 |
Miscellaneous SON corrections |
ZTE Corporation, Sanechips, |
| R2-2407000 |
Corrections on SPR configuration |
CATT |
| R2-2407038 |
RRC Corrections for SON/MDT |
Samsung, Ericsson |
| R2-2407118 |
RAN2 impacts of RAN3 reply LS on MDT for NPN (R2-2406218/R3-243892) |
Nokia |
| R2-2407217 |
Addressing SONMDT issues |
Ericsson |
| R2-2407337 |
Correction to 38.306 on SON reports |
Huawei, HiSilicon |
| R2-2407367 |
SCG failure information in fast MCG recovery MRO |
Sharp |
| R2-2407373 |
Correction on the successPSCell-Config handling |
Google |
| R2-2407663 |
Rel-18 SONMDT Corrections |
Ericsson, Nokia, Samsung |
| R2-2407871 |
Rel-18 SONMDT Corrections |
Ericsson, Nokia, Samsung |
| 7.14.1 |
Organizational |
|
| R2-2407088 |
Correction of Enhancement on NR QoE management and optimizations for diverse services |
Ericsson |
| R2-2407734 |
Correction of Enhancement on NR QoE management and optimizations for diverse services |
Ericsson, CATT, ZTE, Google, Huawei, Samsung |
| 7.14.2 |
Corrections |
|
| R2-2406998 |
Consideration on QoE configuration release during inter-RAT mobility |
ZTE Corporation, Sanechips |
| R2-2407001 |
The correction for RRC spec for R18 QoE |
CATT |
| R2-2407090 |
Release of QoE measurements at successful handover from LTE |
Ericsson, Nokia, Nokia Shanghai Bell |
| R2-2407168 |
Miscellaneous Stage-2 corrections on R18 QoE |
Nokia, Nokia Shanghai Bell,China Unicom |
| R2-2407336 |
Correction on area scope checking for MBS QoE |
Huawei, HiSilicon |
| R2-2407339 |
Correction on application layer measurement report re-submittion |
Google |
| R2-2407731 |
Miscellaneous Stage-2 corrections on R18 QoE |
Nokia, Nokia Shanghai Bell,China Unicom |
| R2-2407735 |
Report of [AT127][504][QoE] Release of QoE configurations (ZTE) |
ZTE Corporation |
| 7.15.1 |
Organizational |
|
| R2-2406209 |
Reply LS on Sidelink Feature Co-configuration (R1-2405530; contact: OPPO) |
RAN1 |
| R2-2406264 |
Discussion on LS R1-2405530 |
OPPO |
| 7.15.2 |
Corrections |
|
| R2-2406265 |
Miscellaneous correction on R18 SL Evolution |
OPPO |
| R2-2406316 |
Correction on selection of resources for MCSt |
CATT, CICTCI |
| R2-2406518 |
Discussion on SR prioritization regarding SL transmission |
ASUSTeK |
| R2-2406554 |
TP for SL CA in TS38300 |
NEC |
| R2-2406584 |
Discussion on MAC corrections when supporting IUC and DRX in Co-Ex |
LG Electronics France |
| R2-2406596 |
Miscellaneous corrections for SL evolution |
Huawei, HiSilicon |
| R2-2406700 |
Correction on legacy carrier selection |
ZTE Corporation, Sanechips |
| R2-2406746 |
Discussion on carrier selection for SL MAC CE(s) |
LG Electronics Inc. |
| R2-2406806 |
Correction to per-LCH carrier set restriction in LCP |
Ericsson |
| R2-2407131 |
Carrier reselection for IUC |
Nokia |
| R2-2407372 |
Correction on setuprelease type sidelink fields handling |
Google |
| R2-2407381 |
MAC corrections on Release-18 Sidelink evolution |
LG Electronics Inc. |
| R2-2407388 |
Rapporteur Stage 2 Corrections for NR Sidelink Evolution |
InterDigital France R&D, SAS, NEC |
| R2-2407581 |
MAC corrections on Release-18 Sidelink evolution |
LG Electronics Inc. |
| R2-2407582 |
Miscellaneous correction on R18 SL Evolution |
OPPO |
| R2-2407583 |
Rapporteur Stage 2 Corrections for NR Sidelink Evolution |
InterDigital, NEC |
| R2-2407594 |
TP for resource selection when supporting both IUC and Co-Ex |
Apple, Ericsson |
| R2-2407603 |
MAC corrections on Release-18 Sidelink evolution |
LG Electronics Inc. |
| R2-2407800 |
Discussion on legacy carrier selection |
ZTE Corporation, Sanechips |
| R2-2407865 |
MAC correction on Release-18 Sidelink evolution |
LG |
| R2-2407878 |
MAC correction on Release-18 Sidelink evolution" |
LG |
| 7.17.1 |
Organizational |
|
| R2-2407186 |
Corrections to TS 38.300 for R18 MUSIM |
China Telecom, Samsung |
| R2-2407870 |
Corrections to TS 38.300 for R18 MUSIM |
China Telecom, Samsung |
| 7.17.3 |
Corrections |
|
| R2-2406715 |
Discussion on configuration for temporary capability restriction |
Huawei, HiSilicon |
| R2-2407077 |
Further discussion on MUSIM capability restriction signalling |
Ericsson |
| R2-2407104 |
Clarification on DAPS Handover for Dual TX/RX MUSIM operation |
Nokia |
| R2-2407321 |
Further Clarification on the Reconfiguration Failure Processing |
ZTE Corporation, Sanechips |
| R2-2407515 |
Remaining issues on MUSIM |
Samsung Electronics Czech |
| R2-2407845 |
Correction on NR MUSIM enhancements |
vivo |
| R2-2407852 |
Correction on NR MUSIM enhancements |
vivo |
| R2-2407864 |
Correction on NR MUSIM enhancements |
vivo |
| 7.19.1 |
Organizational |
|
| R2-2406205 |
Reply LS on Rel-18 RedCap enhancements to address remaining ENs in TS 23.502 (C1-243517; contact: Huawei) |
CT1 |
| R2-2407314 |
Miscellaneous corrections on TS 38.304 for eRedCap |
Huawei, HiSilicon |
| R2-2407554 |
Miscellaneous corrections on TS 38.321 for eRedCap |
vivo (Rapporteur) |
| 7.19.2 |
Other |
|
| R2-2406442 |
Discussion on 2-step RACH for eRedCap |
vivo, Guangdong Genius |
| R2-2407315 |
Corrections on some features application to (e)RedCap UE |
Huawei, HiSilicon |
| R2-2407534 |
MAC correction for eRedCap |
ZTE Corporation, Sanechips |
| R2-2407656 |
Corrections on some features application to (e)RedCap UE |
Huawei, HiSilicon |
| 7.20.1 |
Organizational |
|
| R2-2406214 |
Reply to RAN2 LS on type 3 PH value for the serving cell configured with mTRP (R1-2405619; contact: MediaTek) |
RAN1 |
| 7.20.2 |
Corrections |
|
| R2-2406488 |
Correction to MIMO Evolution |
Samsung |
| R2-2406489 |
Remaining issues on PHR for mTRP STx2P |
Samsung |
| R2-2406519 |
Discussion on remaining issue for 8Tx in MAC specification |
ASUSTeK |
| R2-2406574 |
Correction on simultaneousU-TCI-UpdateListx |
CATT |
| R2-2406778 |
Correction on unified TCI state for SRS |
vivo |
| R2-2406807 |
Random Access problem for SpCell with two TAGs |
Langbo |
| R2-2406808 |
Clarification on the codebook type request in the UE capability enquiry |
Nokia Corporation |
| R2-2406915 |
Remaining issue on STx2P PHR |
LG Electronics Inc. |
| R2-2407202 |
Correction on PHR for STx2P in NR-DC |
Huawei, HiSilicon |
| R2-2407434 |
Further Considerations on Harmonizing the PHR for Different Features |
ZTE Corporation |
| R2-2407843 |
Correction to PHR for multi-TRP multi-panel scheme in MIMO Evolution |
Samsung |
| R2-2407844 |
Correction on MIMOevo |
Ericsson |
| R2-2407850 |
Correction to PHR for multi-TRP multi-panel scheme in MIMO Evolution |
Samsung |
| R2-2407851 |
Correction on MIMOevo |
Ericsson |
| R2-2407866 |
Correction on MIMOevo |
Ericsson |
| 7.21.1 |
Organizational |
|
| R2-2407419 |
Miscellaneous corrections for further NR coverage enhancements in RRC |
Huawei, HiSilicon |
| R2-2407517 |
Miscellaneous corrections on further NR Coverage enhancements in MAC |
ZTE Corporation |
| R2-2407640 |
Miscellaneous corrections for further NR coverage enhancements in RRC |
Huawei, HiSilicon, Philips International B.V., Ericsson, Lenovo |
| R2-2407641 |
Miscellaneous corrections on further NR Coverage enhancements in MAC |
ZTE Corporation |
| 7.21.2 |
Other Essential corrections |
|
| R2-2406811 |
Addition of missing prerequisite in the description of capability dynamicWaveformSwitchIntraCA-r18 |
Lenovo |
| R2-2406922 |
Conditional Presence for absence of field preambleTransMax-Msg1-Repetition |
Ericsson |
| R2-2407275 |
RRC Correction on Msg1 based SI request with Msg1 Repetition |
Philips International B.V. |
| R2-2407278 |
Correction on posSIB(s) acquisition for Msg1 based SI request with Msg1 Repetition [TEI17 SI-SCHEDULING] |
Philips International B.V., Ericsson |
| R2-2407420 |
Clarifications on initilization of RACH parameters during repetition fallback |
Huawei, HiSilicon |
| 7.24.1 |
TEI proposals by Other Groups |
|
| R2-2406206 |
Reply LS on 5GS missing CBC support for shared networks (C1-243686; contact: Ericsson) |
CT1 |
| R2-2406231 |
LS on intra-band EN-DC channel spacing (R4-2410693; contact: Huawei) |
RAN4 |
| R2-2406243 |
Reply LS Mitigation of Downgrade attacks (S3-242367; contact: Apple) |
SA3 |
| R2-2406261 |
Discussion on LS R4-2410693 |
OPPO |
| R2-2406458 |
SDT signalling optimization for partial context transfer |
ZTE Corporation, Sanechips |
| R2-2406465 |
Paging monitoring for extended CG period [CG-SDT-Enh] |
ZTE Corporation, Sanechips, Mediatek, Qualcomm, Ericsson |
| R2-2406660 |
Impacts on RAN2 for supporting of SDT signalling optimization for partial context transfer |
Sharp |
| R2-2406833 |
Discussion on LS on intra-band EN-DC channel spacing |
CATT |
| R2-2406834 |
Capability update for intraBandENDC-Support |
CATT |
| R2-2406835 |
DRAFT Reply LS on intra-band EN-DC channel spacing |
CATT |
| R2-2406929 |
Impact of SDT signalling optimization for partial context transfer on RAN2 |
Huawei, HiSilicon |
| R2-2406930 |
Correction for Paging monitoring during SDT [CG-SDT-Enh] |
Huawei, HiSilicon |
| R2-2407229 |
Discussion on LS to RAN3 |
Ericsson, Nokia |
| R2-2407329 |
Consideration on the intra-band EN-DC Channel Spacing |
ZTE Corporation, Sanechips |
| R2-2407330 |
Draft Reply LS on the intra-band EN-DC Channel Spacing |
ZTE Corporation, Sanechips |
| R2-2407466 |
Discussion on intra-band EN-DC channel spacing |
Huawei, HiSilicon |
| R2-2407467 |
Introduction of new capability for intra-band EN-DC channel spacing |
Huawei, HiSilicon |
| R2-2407468 |
Introduction of new capability for intra-band EN-DC channel spacing |
Huawei, HiSilicon |
| R2-2407469 |
Reply LS on intra-band EN-DC channel spacing |
Huawei, HiSilicon |
| R2-2407501 |
Reply LS on SDT signalling optimization for partial context transfer |
ZTE Corporation, Sanechips |
| R2-2407746 |
Reply LS on SDT signalling optimization for partial context transfer |
ZTE Corporation, Sanechips |
| R2-2407803 |
Paging monitoring for extended CG period [CG-SDT-Enh] |
ZTE Corporation, Sanechips, Mediatek, Qualcomm, Ericsson |
| R2-2407816 |
Reply LS on SDT signalling optimization for partial context transfer |
RAN2 |
| 7.24.2.1 |
2Rx XR |
|
| R2-2406933 |
Cell barring depending on the UE band for 2Rx XR UE |
Huawei, HiSilicon, Xiaomi Communications, Ericsson, LG Electronics |
| 7.24.2.2 |
Other RAN2 TEI-18 |
|
| R2-2406441 |
Discussion on issues for emergency call with barringExemptEmergencyCall |
vivo, China Telecom, China Unicom, Guangdong Genius |
| R2-2406461 |
Open issues for emergency calls for 2RX UEs |
ZTE Corporation, Sanechips |
| R2-2406462 |
Correction to barring exemption for (e)Redcap and XR 2RX UEs [EM_Call_Exemption] |
ZTE Corporation, Sanechips |
| R2-2406511 |
Discussion on cell barring and barring exemption |
Qualcomm Incorporated |
| R2-2406512 |
Clarifications on cell barring [EM_Call_Exemption] |
Qualcomm Incorporated |
| R2-2406513 |
Clarifications on cell barring [EM_Call_Exemption] |
Qualcomm Incorporated |
| R2-2406859 |
Discussion on TEI18 enhancement to measurement report |
Samsung Electronics |
| R2-2406931 |
Introduction of barring exemption for emergency call [EM_Call_Exemption] |
Huawei, HiSilicon |
| R2-2406932 |
Corrections on the barring exemption for emergency call [EM_Call_Exemption] |
Huawei, HiSilicon |
| R2-2407182 |
Correction on frequency introduced for CIO [CIO_in_ReportConfig] |
Ericsson, Samsung, NTT Docomo, INC., KDDI, Qualcomm Incorporated |
| R2-2407493 |
Discussion on remaining issues on cell individual offset |
Samsung, Ericsson |
| R2-2407505 |
Introduction of a UE capability for the barring exemption for emergency call [EM_Call_Exemption] |
Huawei, HiSilicon |
| R2-2407510 |
Correction to enteringLeavingReport condition |
LG Electronics France |
| R2-2407513 |
Correction to EnteringLeavingReport condition |
LG Electronics |
| R2-2407521 |
NES for NCR |
LG Uplus |
| R2-2407749 |
Discussion on TEI18 enhancement to measurement report |
Samsung Electronics |
| R2-2407783 |
Correction on enhancements to measurement report [meas_report_enh] |
Samsung |
| R2-2407804 |
Correction to barring exemption for (e)Redcap and XR 2RX UEs [EM_Call_Exemption] |
ZTE Corporation, Sanechips |
| R2-2407817 |
Correction to EnteringLeavingReport condition |
LG Electronics., Ericsson, Qualcomm Inc., ZTE, Apple, MediaTek Inc. |
| R2-2407820 |
Correction to barring exemption for (e)Redcap and XR 2RX UEs [EM_Call_Exemption] |
ZTE Corporation, Sanechips |
| R2-2407822 |
Correction to EnteringLeavingReport condition |
LG Electronics., Ericsson, Qualcomm Inc., ZTE, Apple, MediaTek Inc. |
| R2-2407829 |
Introduction of barring exemption for emergency call [EM_Call_Exemption] |
Huawei, HiSilicon |
| R2-2407833 |
Correction to EnteringLeavingReport condition |
LG Electronics, Ericsson, Qualcomm Inc., ZTE, Apple, MediaTek Inc., Samsung |
| R2-2407882 |
Correction to EnteringLeavingReport condition [meas_report_enh] |
LG Electronics, Ericsson, Qualcomm Inc., ZTE, Apple, MediaTek Inc., Samsung |
| 7.25.1 |
RAN4 led items |
|
| R2-2406226 |
Reply LS to RAN2 on RRM enhancements for NR FR2 HST (R4-2410285; contact: Samsung) |
RAN4 |
| R2-2406230 |
Reply LS on inter-frequency neighbour cells supporting NR dedicated spectrum less than 5 MHz for FR1 (R4-2410600; contact: Qualcomm) |
RAN4 |
| R2-2406339 |
Correction on inter-frequency configuration for less than 5MHz |
Huawei, HiSilicon |
| R2-2406604 |
Clarification of offsetThresholdTA-r18 for NR ATG |
Huawei, HiSilicon, CMCC |
| R2-2406836 |
Dummify the capability bit multiRx-FR2-Preference-r18 |
CATT, Apple, Intel Corporation |
| R2-2406837 |
Dummify the capability bit multiRx-FR2-Preference-r19 |
CATT, Apple, Intel Corporation |
| R2-2406944 |
Introduction of unknown SCell activation enhancement |
Huawei, HiSilicon, Apple |
| R2-2407178 |
MAC correction on fast unknown SCell activation |
Ericsson |
| R2-2407179 |
RRC correction on fast unknown SCell activation |
Ericsson |
| R2-2407247 |
Clarification on highSpeedMeasFlagFR2 for HST FR2 RRM |
Samsung |
| R2-2407322 |
Correction on asymmetricBandwidthCombinationSet for the 3M |
ZTE Corporation, Sanechips |
| R2-2407335 |
Correction on the configuration parameter highSpeedMeasFlagFR2 for FR2 HST |
Huawei, HiSilicon |
| R2-2407379 |
Discussion on RRM enhancements for NR FR2 HST |
ZTE Corporation, Sanechips |
| R2-2407380 |
Discussion on ATG |
ZTE Corporation, Sanechips |
| R2-2407399 |
Miscellaneous corrections for fast unknown SCell activation |
Huawei, HiSilicon |
| R2-2407400 |
Miscellaneous corrections for fast unknown SCell activation |
Huawei, HiSilicon |
| R2-2407530 |
Clarifications for ATG timing advance reporting procedures |
Samsung |
| R2-2407761 |
Correction on asymmetricBandwidthCombinationSet for the 3M |
ZTE Corporation, Sanechips |
| R2-2407762 |
Dummify the capability bit multiRx-FR2-Preference-r18 |
CATT, Apple, Intel Corporation |
| R2-2407763 |
Dummify the capability bit multiRx-FR2-Preference-r19 |
CATT, Apple, Intel Corporation |
| R2-2407792 |
Clarification on highSpeedMeasFlagFR2 for HST FR2 RRM |
Samsung |
| R2-2407806 |
Report of [AT127][024][ATG] Clarification on SCS for Timing Advance reporting |
Samsung |
| R2-2407815 |
Introduction of unknown SCell activation enhancement |
Huawei, HiSilicon, Apple |
| 7.25.2 |
RAN1 led items |
|
| R2-2406317 |
Correction on PDCCH monitoring for Multi-cell scheduling |
CATT |
| R2-2406815 |
Removal of term ‘legacy’ from the description of dci-FormatsMC |
Lenovo |
| R2-2406945 |
Miscellaneous corrections for Multi-Carrier enhancements |
Huawei, HiSilicon |
| R2-2407424 |
Clarification on deactivated or dormant cells in multi-cell scheduling |
Samsung, ZTE Corporation, Sanechips, NTT DOCOMO, OPPO |
| R2-2407463 |
Reply LS on UE capability for multi-carrier enhancements |
RAN2 |
| R2-2407764 |
Miscellaneous corrections for Multi-Carrier enhancements |
Huawei, HiSilicon, Lenovo, NTT DOCOMO INC. |
| 8.0 |
General |
|
| R2-2406223 |
Reply LS on FS_VMR_Ph2 solution impacts to RAN (R3-243961; contact: Qualcomm) |
RAN3 |
| R2-2406233 |
Reply LS RP-240891 on NTZ solution impacts to RAN (RP-241668; contact: InterDigital) |
RAN |
| R2-2406235 |
LS on NTZ solution impacts to RAN (S2-2407355; contact: LGE & Ericsson) |
SA2 |
| R2-2406239 |
LS on questions regarding FS_VMR_Ph2 (S2-24073455; contact: Samsung) |
SA2 |
| R2-2407087 |
On new ASN.1 review process |
Ericsson |
| R2-2407190 |
ASN.1 Review Modernization |
Nokia Corporation |
| R2-2407786 |
Report of [AT127][004][ASN.1 Modernization] F2F offline (Nokia) |
Nokia |
| 8.1 |
AI/ML for NR air interface |
|
| R2-2406224 |
LS on terminology definitions for AI-ML in NG-RAN (R3-243969; contact: Ericsson) |
RAN3 |
| 8.1.1 |
Organizational |
|
| R2-2406212 |
Reply LS on data collection to enable ML model training and inference in 5GC for Direct AI/ML based positioning (R1-2405578; contact: Ericsson) |
RAN1 |
| R2-2406236 |
LS on data collection to enable ML model training and inference in 5GC for Direct AI/ML based positioning (S2-2405833; contact: vivo) |
SA2 |
| R2-2407252 |
On RAN3 inputs about AIML Terminology |
Ericsson |
| 8.1.2.2 |
LCM for UE-sided model for Beam Management use case |
|
| R2-2406259 |
Reporting of applicable functionalities |
OPPO |
| R2-2406260 |
Other LCM for UE-sided model for Beam Management use case |
OPPO |
| R2-2406335 |
LCM for UE-sided model for Beam Management use case |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2406381 |
Report of [POST126][032][AI/ML PHY] LCM (Intel/Samsung)_Phase 2 |
Intel Corporation |
| R2-2406382 |
Beam management UE-sided model LCM signaling |
Intel Corporation |
| R2-2406387 |
Discussion on LCM for UE-sided model for Beam Management |
vivo |
| R2-2406537 |
Discussion on the LCM for UE-sided Model for Beam Management |
Fujitsu |
| R2-2406564 |
Discussion on LCM for UE-sided model |
NEC |
| R2-2406578 |
Availability and Applicability Reporting for UE-side Functionality |
MediaTek Inc. |
| R2-2406613 |
Some aspects for model inference |
Sony |
| R2-2406643 |
On LCM for UE-sided models |
Qualcomm Incorporated |
| R2-2406672 |
Further discussion on LCM procedure of UE-sided model for AI/ML based beam management |
Apple |
| R2-2406701 |
Discussion on LCM for UE-sided model for BM |
Xiaomi |
| R2-2406758 |
Discussion on LCM for UE-sided model for Beam Management |
Spreadtrum Communications |
| R2-2406827 |
Discussion on LCM for UE-sided model for Beam Management use case |
CATT |
| R2-2406876 |
LCM for UE-sided model in beam management |
Lenovo |
| R2-2406934 |
Discussion on LCM for UE-sided model for Beam Management use case |
Huawei, HiSilicon |
| R2-2406963 |
Discussion on LCM for UE-sided model for BM |
CMCC |
| R2-2407066 |
LCM for UE-side model for Beam Management |
Nokia |
| R2-2407154 |
Discussion on LCM for UE-sided model for Beam Management |
Sharp |
| R2-2407164 |
Remaining issues in LTM for UE-sided model |
Samsung |
| R2-2407165 |
Report of [POST126][032][AI/ML PHY] LCM (Intel/Samsung) – Phase 1 |
Samsung |
| R2-2407189 |
Applicable functionality reporting |
InterDigital |
| R2-2407251 |
LCM for UE-side models for beam management |
Ericsson |
| R2-2407365 |
Functionality definition and applicability related report |
LG Electronics |
| R2-2407435 |
Further Discussion on LCM for UE side Model |
ZTE Corporation |
| R2-2407457 |
LCM for UE-sided model for beam management use case |
TCL |
| R2-2407471 |
Considerations for the Five Functionalities Conditions |
Kyocera |
| R2-2407485 |
Discussion on Functionality-based LCM of UE-sided Model for Beam Management Use Cases |
CEWiT |
| R2-2407488 |
Discussion on LCM for UE-Side Models (Beam Management) |
Futurewei |
| R2-2407848 |
LS on applicable functionality reporting for beam management UE-sided model |
RAN2 |
| 8.1.2.3 |
LCM for Positioning use case |
|
| R2-2406334 |
Lifecycle management for positioning use-cases |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2407456 |
Discussion on Dynamic Capability Report for Positioning |
Sharp |
| 8.1.3 |
NW side data collection |
|
| R2-2406258 |
Data Collection for Network Side Model Training |
OPPO |
| R2-2406383 |
Enhancements for NW-side model training data collection |
Intel Corporation |
| R2-2406388 |
Discussion on NW side data collection framework |
vivo |
| R2-2406498 |
AIML MDT-based data collection for NW-side model |
NEC |
| R2-2406503 |
NW side data collection |
TCL |
| R2-2406538 |
Discussion on NW side Data Collection for Beam Management |
Fujitsu |
| R2-2406539 |
Discussion on NW side Data Collection for Positioning |
Fujitsu |
| R2-2406573 |
Enhanced MDT for Data collection for Network Side Model Training |
MediaTek Inc. |
| R2-2406644 |
On Network Side Data Collection |
Qualcomm Incorporated |
| R2-2406673 |
Further discussion on NW-sided data collection |
Apple |
| R2-2406702 |
Discussion on NW side data collection |
Xiaomi |
| R2-2406776 |
Discussion on NW side data collection for AI-ML based positioning accuracy enhancement |
Baicells |
| R2-2406828 |
Consideration on NW side data collection |
CATT |
| R2-2406877 |
Data collection for NW-sided model training in beam management |
Lenovo |
| R2-2406878 |
Data collection for NW-sided model training in positioning |
Lenovo |
| R2-2406964 |
Discussion on NW side data collection |
CMCC |
| R2-2407040 |
Discussion on NW-side data collection |
Samsung R&D Institute UK |
| R2-2407067 |
Data Collection for Training of NW-side models |
Nokia |
| R2-2407243 |
Data Collection for Network-Sided Model Training |
InterDigital Inc. |
| R2-2407248 |
NW-side data collection for beam management use cases |
Ericsson |
| R2-2407331 |
Discussion on NW-sided data collection for training |
Huawei, HiSilicon |
| R2-2407366 |
NW side data collection |
LG Electronics |
| R2-2407417 |
Discussion on NW-side Data Collection for Positioning |
Sharp |
| R2-2407436 |
Further Consideration on NW side Data Collection |
ZTE Corporation |
| R2-2407489 |
Discussion on Data Collection for NW-side Model Training |
Futurewei |
| R2-2407535 |
Discussion on Network Side Data Collection |
Rakuten Mobile, Inc |
| 8.1.4 |
UE side data collection |
|
| R2-2406340 |
Remaining issues for Data Collection for UE side Model training |
NEC |
| R2-2406384 |
Discussion on UE-sided model training data collection |
Intel Corporation |
| R2-2406389 |
Discussion on UE side data collection |
vivo |
| R2-2406407 |
Data collection for UE side model training |
Xiaomi |
| R2-2406572 |
Discussion on the FFS Issues of UE-Side Data Collection |
MediaTek Inc. |
| R2-2406645 |
On UE Side Data Collection |
Qualcomm Incorporated |
| R2-2406674 |
Further discussion on UE-sided data collection |
Apple |
| R2-2406829 |
Consideration on UE side data collection |
CATT |
| R2-2406965 |
Discussion on UE side data collection |
CMCC, China Unicom, NTT DOCOMO, ZTE, OPPO |
| R2-2407068 |
Data Collection for Training of UE-side models |
Nokia |
| R2-2407209 |
RAN2 inputs to TR 38.843 |
Ericsson |
| R2-2407250 |
UE-side Data Collection |
Ericsson |
| R2-2407332 |
Discussion on UE-sided data collection for training |
Huawei, HiSilicon, CAICT |
| R2-2407413 |
Data collection for the training of a UE-sided model |
InterDigital Inc., Ericsson, Nokia, T-Mobile USA Inc., BT PLC., Deutsche Telekom, Verizon, NTT Docomo, Charter Communications Inc. |
| R2-2407437 |
Further Consideration on UE side Data Collection |
ZTE Corporation |
| R2-2407490 |
Discussion on Data Collection for UE-side Model Training |
Futurewei |
| R2-2407503 |
Remaining FFSs on data collection options for UE-side model training |
Samsung |
| R2-2407773 |
Report of [AT127][021][AIML PHY] UE side data collection |
InterDigital Inc. (Rapporteur) |
| R2-2407785 |
Data Collection Table modified online |
Chairlady |
| R2-2407802 |
RAN2 inputs to TR 38.843 |
Ericsson |
| R2-2407807 |
RAN2 inputs to TR 38.843 |
Ericsson |
| R2-2407808 |
RAN2 inputs to TR 38.843 |
RAN2 |
| R2-2407832 |
RAN2 inputs to TR 38.843 |
RAN2 |
| 8.2.1 |
Organizational |
|
| R2-2406237 |
LS on Clarification of requirements for Ambient IoT (S2-2407231; contact: Ericsson) |
SA2 |
| R2-2406271 |
TP for TR 38.769 update |
Huawei, CMCC, T-Mobile USA |
| 8.2.2 |
Functionality aspects |
|
| R2-2406362 |
Discussion on protocol stack for ambient IOT |
Xiaomi |
| R2-2406377 |
Required functions for A-IoT |
Intel Corporation |
| R2-2406390 |
Discussion on functionality aspects for Ambient IoT |
vivo |
| R2-2406453 |
Considerations for functionality aspects |
Semtech Neuchatel SA |
| R2-2406459 |
A-IoT Functionality |
ZTE Corporation, Sanechips |
| R2-2406482 |
Discussion on the Functionality Aspects for Ambient IoT |
CATT |
| R2-2406505 |
Ambient-IoT Functionality Aspects |
NEC |
| R2-2406540 |
Discussions on Functionality Aspect of Ambient IoT |
Fujitsu |
| R2-2406582 |
Inventory procedure without permanent device ID |
VODAFONE Group Plc |
| R2-2406590 |
Energy Status report |
Vodafone, Qualcomm, Nokia, Interdigital, Xiaomi, Samsung, Deutsche Telekom |
| R2-2406608 |
Discussions on functionalities required for AIoT |
Samsung |
| R2-2406614 |
Considerations on functionality aspects for Ambient IoT |
Sony |
| R2-2406654 |
Ambient IoT transport block size and MAC layer segmentation |
MediaTek Inc., Samsung, vivo, ZTE Corporation, Sanechips, Qualcomm Incorporated |
| R2-2406656 |
Ambient IoT data transmission after initial access |
MediaTek Inc. |
| R2-2406666 |
Funcitonal Aspects of A-IoT devices |
Apple |
| R2-2406709 |
Functionality for Ambient IOT |
InterDigital |
| R2-2406737 |
Discussion on functionality aspects of Ambient IoT |
China Telecom |
| R2-2406751 |
Discussion on the functionalities required for Ambient IoT |
Spreadtrum Communications |
| R2-2406769 |
Discussion on functionalities required for A-IoT |
OPPO |
| R2-2406812 |
Considerations on functionality aspects for Ambient IoT |
Lenovo |
| R2-2406818 |
Functionality aspects for A-IoT |
Ericsson |
| R2-2406941 |
A-IoT functionalities |
Huawei, HiSilicon |
| R2-2406942 |
Views on the segmentation of A-IoT |
Huawei, HiSilicon, Wiliot Ltd., Quanray, Telit Communications S.p.A., Nordic Semiconductor ASA, China Unicom, China Telecom, China Southern Power Grid, NTT DOCOMO INC., LG Electronics Inc., Spreadtrum Communications, Xiaomi, ASUSTeK, Kyocera, ETRI, CAICT, |
| R2-2406977 |
Discussion on functionality for A-IoT |
CMCC |
| R2-2407063 |
Discussion on security aspects for Ambient IoT |
NTT DOCOMO, INC. |
| R2-2407126 |
Discussion on security related aspects of Ambient IoT devices |
T-Mobile USA Inc., Ericsson |
| R2-2407132 |
AIoT Functionality aspects |
Nokia |
| R2-2407231 |
Discussion on security related aspects of Ambient IoT devices |
T-Mobile USA Inc., Ericsson |
| R2-2407290 |
Discussion on functionality aspects of ambient IoT |
LG Electronics Inc. |
| R2-2407319 |
Views on Functionality Aspects of Ambient IoT |
Qualcomm Incorporated |
| R2-2407342 |
Discussions on functionalities required for A-IoT Communication |
HONOR |
| R2-2407445 |
Functionalities for Ambient IoT |
Kyocera |
| R2-2407504 |
Discussions on functionality aspects for AIoT |
Futurewei |
| R2-2407567 |
Views on the segmentation of A-IoT |
Huawei, HiSilicon, Wiliot Ltd., Quanray, Telit Communications S.p.A., Nordic Semiconductor ASA, China Unicom, China Telecom, China Southern Power Grid, NTT DOCOMO INC., CMCC, LG Electronics Inc., Spreadtrum Communications, Xiaomi, ASUSTeK, Kyocera, ETRI, |
| R2-2407830 |
Draft LS on data block sizes for Ambient IoT |
MediaTek |
| R2-2407831 |
LS on data block sizes for Ambient IoT |
RAN2 |
| 8.2.3 |
A-IoT Paging |
|
| R2-2406378 |
Consideration on initial trigger message |
Intel Corporation |
| R2-2406391 |
Discussion on AIoT Paging |
vivo |
| R2-2406426 |
Discussion on A-IOT paging procedure |
Xiaomi |
| R2-2406483 |
Discussion on Paging for Ambient IoT |
CATT |
| R2-2406501 |
Ambient IoT device paging |
TCL |
| R2-2406520 |
Discussion on Ambient IoT paging message |
ASUSTeK |
| R2-2406541 |
Discussions on AIoT paging |
Fujitsu |
| R2-2406609 |
Discussion on A-IoT paging |
Samsung |
| R2-2406615 |
Considerations on paging for Ambient IoT |
Sony |
| R2-2406651 |
Paging for Ambient IoT |
Qualcomm Incorporated |
| R2-2406655 |
Procedures and signalling for ambient IoT paging |
MediaTek Inc. |
| R2-2406681 |
Discussion on Ambient IoT Paging |
Apple |
| R2-2406710 |
Paging Related Aspects for Ambient IOT |
InterDigital |
| R2-2406718 |
Discussion on paging procedure for Ambient IoT |
OPPO |
| R2-2406738 |
Discussion on Ambient IoT Paging |
China Telecom |
| R2-2406747 |
Discussion on paging procedure of A-IoT |
Spreadtrum Communications |
| R2-2406856 |
Ambient-IoT Paging |
NEC |
| R2-2406879 |
Discussion on paging procedure for Ambient IoT |
Lenovo |
| R2-2406960 |
Discussion on A-IoT paging |
CMCC |
| R2-2407021 |
Discussion on Paging for A-IoT |
Transsion Holdings |
| R2-2407136 |
Discussion on A-IoT paging message |
NTT DOCOMO, INC. |
| R2-2407148 |
Further consideration on paging procedure for AIoT |
ZTE Corporation, Sanechips |
| R2-2407203 |
Ambient IoT identifiers for A-IoT paging |
Panasonic |
| R2-2407212 |
Paging procedures for Ambient IoT |
Nokia France |
| R2-2407222 |
Discussion on Paging aspects for Ambient-IoT |
Continental Automotive |
| R2-2407244 |
Discussion on DL messages for Ambient IoT UEs |
Ericsson |
| R2-2407261 |
Discussion on A-IoT paging |
Sharp |
| R2-2407283 |
Discussion on A-IoT paging |
LG Electronics Inc. |
| R2-2407343 |
Discussion on A-IoT Paging |
HONOR |
| R2-2407444 |
Consideration of paging for Ambient IoT |
Kyocera |
| R2-2407508 |
Discussions on AIoT paging |
Futurewei |
| R2-2407533 |
Discussion on Paging procedure for Ambient IoT |
Philips International B.V. |
| R2-2407547 |
Discussion on A-IOT Paging related aspects |
Rakuten Mobile, Inc |
| 8.2.4 |
A-IoT Random Access |
|
| R2-2406341 |
Random Access for Ambient IoT device |
NEC |
| R2-2406361 |
Discussion on access procedure for ambient IOT |
Xiaomi |
| R2-2406379 |
Consideration on A-IoT Random access |
Intel Corporation |
| R2-2406392 |
Random Access Procedure for A-IoT Device |
vivo |
| R2-2406454 |
Considerations for Random Access |
Semtech Neuchatel SA |
| R2-2406460 |
Unified random-access procedure for A-IoT |
ZTE Corporation, Sanechips |
| R2-2406484 |
Discussion on the Random Access for Ambient IoT |
CATT |
| R2-2406502 |
Random Access for Ambient IOT |
TCL |
| R2-2406521 |
Discussion on Ambient IoT access message |
ASUSTeK |
| R2-2406542 |
Discussions on AIoT Random Access |
Fujitsu |
| R2-2406616 |
Considerations on random access aspects for Ambient IoT |
Sony |
| R2-2406682 |
Discussion on Random Access for Ambient IoT |
Apple |
| R2-2406711 |
Random Access Procedure for Ambient IOT |
InterDigital |
| R2-2406716 |
A-IoT random access procedure |
Huawei, HiSilicon |
| R2-2406752 |
Discussion on random access of Ambient IoT |
Spreadtrum Communications |
| R2-2406764 |
Further discussions on A-IoT random access |
ETRI |
| R2-2406770 |
Discussion on random access for A-IoT |
OPPO |
| R2-2406786 |
Discussion on UL multiple access |
Ericsson |
| R2-2406880 |
Discussion on random access for Ambient IoT |
Lenovo |
| R2-2406899 |
Random access procedure for Ambient IoT |
China Telecom |
| R2-2406987 |
Further consideration on Ambient IoT random access |
CMCC |
| R2-2407022 |
Discussion on Random Access for A-IoT |
Transsion Holdings |
| R2-2407207 |
Discussion on A-IoT random access procedure |
NTT DOCOMO, INC. |
| R2-2407220 |
Random access for Ambient IoT |
Nokia France |
| R2-2407262 |
Discussion on A-IoT random access |
Sharp |
| R2-2407265 |
Discussion on random access aspects for Ambient IoT |
LG Electronics Inc. |
| R2-2407317 |
Views on Random Access Aspects of Ambient IoT |
Qualcomm Incorporated |
| R2-2407344 |
Discussion on A-IoT random access |
HONOR |
| R2-2407385 |
Discussion on random access for ambient IoT |
Google Ireland Limited |
| R2-2407443 |
Consideration of random access of Ambient IoT |
Kyocera |
| R2-2407458 |
Further discussion on Ambient IoT random access |
Samsung Electronics Czech |
| R2-2407509 |
Discussions on AIoT random access |
Futurewei |
| R2-2407536 |
Discussion on Random Access procedure for Ambient IoT |
Philips International B.V. |
| R2-2407542 |
Discussion on Failure Handling |
Rakuten Mobile, Inc |
| 8.2.5 |
Topology 2 considerations |
|
| R2-2406380 |
Topology 2 considerations |
Intel Corporation |
| R2-2406393 |
Discussion on Topology 2 related aspects |
vivo |
| R2-2406406 |
Considerations on TP2 related aspects between BS and UE reader |
Xiaomi |
| R2-2406485 |
Discussion on Topology2 for Ambient IoT |
CATT |
| R2-2406522 |
Consideration on resource and scenario in topology 2 |
ASUSTeK |
| R2-2406543 |
Discussions on topology 2 related aspects |
Fujitsu |
| R2-2406565 |
Discussion on topology 2 related aspects between gNB and reader |
NEC |
| R2-2406610 |
Discussion on A-IoT Topology 2 |
Samsung |
| R2-2406652 |
Topology 2 related aspects |
Qualcomm Incorporated |
| R2-2406657 |
A-IoT Architecture |
MediaTek Inc. |
| R2-2406667 |
Discussion on Topology 2 for A-IoT |
Apple |
| R2-2406712 |
Topology 2 for Ambient IOT |
InterDigital |
| R2-2406720 |
Discussion on topology 2 for Ambient IOT |
OPPO |
| R2-2406748 |
Discussion on topology 2 issues |
Spreadtrum Communications |
| R2-2406785 |
Topology 2 and DO-A for Ambient IoT |
Ericsson |
| R2-2406881 |
Considerations on Topology 2 for Ambient IoT |
Lenovo |
| R2-2406943 |
A-IoT Topology 2 issues |
Huawei, HiSilicon |
| R2-2406961 |
Discussions on topology 2 for A-IoT |
CMCC |
| R2-2407074 |
RAN2 aspects for Topology 2 |
Nokia |
| R2-2407112 |
Discussion on Topology 2 related aspects for Ambient IoT |
China Telecom |
| R2-2407151 |
Consideration on TP2 for AIoT |
ZTE Corporation, Sanechips |
| R2-2407291 |
Discussion on topology 2 considerations of ambient IoT |
LG Electronics Inc. |
| R2-2407442 |
Topology 2 aspects of Ambient IoT |
Kyocera |
| R2-2407450 |
Discussion on topology 2 specific issues for Ambient IoT |
NTT DOCOMO, INC. |
| 8.3.1 |
Organizational |
|
| R2-2406309 |
Text proposal of 38.744 |
OPPO |
| R2-2407781 |
Summary of [AT127][026][AI Mob] Simulation assumptions (OPPO) |
OPPO |
| R2-2407886 |
Report of [POST127][027][AI Mob] Simulation table (Mediatek) |
MediaTek Inc. |
| 8.3.2 |
RRM measurement prediction |
|
| R2-2406308 |
Discussion on cluster based RRM measurement prediction |
BJTU |
| R2-2407451 |
Simulation results for RRM measurement prediction |
Indian Institute of Tech (M), IIT Kanpur |
| R2-2407484 |
Intial simulation results RRM Measurement prediciton |
CEWiT |
| 8.3.2.1 |
Simulation results for RRM measurement prediction |
|
| R2-2406310 |
Discussion on simulation result of RRM measurement |
OPPO |
| R2-2406401 |
Simulation results for RRM measurement prediction |
vivo |
| R2-2406422 |
Evaluation on RRM measurement prediction |
ZTE Corporation |
| R2-2406579 |
Evaluation and Simulation Results for AIML RRM Prediction |
MediaTek Inc. |
| R2-2406664 |
RRM measurement prediction results |
Apple |
| R2-2406665 |
Field data for RRM measurement prediction |
Apple |
| R2-2406703 |
Discussion on RRM prediction simulation result |
Xiaomi |
| R2-2406816 |
Simulation results for RRM measurement prediction |
Qualcomm Incorporated |
| R2-2406824 |
Discussions on simulation results for RRM measurement prediction |
NTT DOCOMO, INC. |
| R2-2406830 |
Simulation results of intra-frequency RRM Measurement Prediction |
CATT, Turkcell |
| R2-2406831 |
Simulation results of inter-frequency RRM Measurement Prediction |
CATT, Turkcell |
| R2-2406860 |
Discussion on the simulation results for RRM measurement prediction |
Samsung Electronics |
| R2-2406935 |
Simulation results for RRM measurement prediction |
Huawei, HiSilicon |
| R2-2406936 |
Discussion on other aspects related to RRM prediction |
Huawei, HiSilicon, China Telecom |
| R2-2406975 |
Initial simulation results for RRM measurement prediction |
CMCC |
| R2-2407092 |
Simulation results for RRM measurement inter-frequency predictions |
Ericsson |
| R2-2407219 |
Simulation results for RRM measurement temporal prediction |
Ericsson |
| R2-2407376 |
Initial simulation results for RRM measurement predictions |
InterDigital Inc. |
| R2-2407479 |
Measurement Reduction based on RRM Measurement Prediction |
Nokia, Nokia Shanghai Bell |
| R2-2407558 |
Evaluation and Simulation Results for AIML RRM Prediction |
MediaTek Inc. |
| R2-2407568 |
Simulation results for RRM measurement prediction |
Qualcomm Incorporated |
| R2-2407849 |
Summary of [POST127][030][AI mobility] RRM simulation assumptions (OPPO) |
OPPO |
| R2-2407885 |
Draft Summary of [POST127][030][AI mobility] RRM simulation assumptions-phase 2(OPPO) |
OPPO |
| 8.3.2.2 |
Other aspects related to RRM measurement prediction |
|
| R2-2406311 |
Discussion on open issue of RRM measurement use case |
OPPO |
| R2-2406385 |
Discussion on AI/ML based RRM measurement prediction |
China Telecom |
| R2-2406402 |
Other aspects related to RRM measurement prediction |
vivo |
| R2-2406423 |
Discussion on RRM measuremnet prediction |
ZTE Corporation |
| R2-2406499 |
AIML mobility RRM measurement prediction |
NEC |
| R2-2406500 |
AI/ML RRM measurement prediction |
TCL |
| R2-2406568 |
Discussion on RRM Measurement Prediction |
Fraunhofer HHI, Fraunhofer IIS |
| R2-2406580 |
Cluster-based Approach for RRM Prediction and Other Aspects |
MediaTek Inc. |
| R2-2406704 |
Discussion on cell and beam RRM prediction |
Xiaomi |
| R2-2406759 |
Discussion on other aspects related to RRM measurement prediction |
Spreadtrum Communications |
| R2-2406825 |
Discussion on other aspects related to RRM measurement prediction |
NTT DOCOMO, INC. |
| R2-2406861 |
Discussion on temporal domain RRM measurement prediction |
Samsung Electronics |
| R2-2406924 |
Discussion on RRM Measurement Prediction |
Sharp |
| R2-2406966 |
Discussion on other aspects related to RRM measurement prediction |
CMCC |
| R2-2407113 |
AI-ML based Inter-frequency measurement prediction |
Rakuten Mobile, Inc |
| R2-2407130 |
RRM measurement prediction |
Lenovo |
| R2-2407287 |
Discussion on RRM Measurement Prediction Framework |
Meta Ireland |
| R2-2407359 |
Discussion on AI aided RRM measurement prediction |
HONOR |
| R2-2407377 |
Other aspects of RRM measurement predictions |
InterDigital Inc. |
| R2-2407480 |
Mobility Optimization based on RRM Measurement Prediction |
Nokia |
| 8.3.3 |
Measurement event predictions |
|
| R2-2406344 |
Target scenarios for measurement event prediction |
NEC |
| R2-2406796 |
Further Discussion on AI based Measurement Event Prediction |
Continental Automotive |
| R2-2407360 |
Discussion on AI aided measurement events prediction |
HONOR |
| R2-2407541 |
Discussion on measurement event predictions |
III |
| 8.3.4.1 |
Simulation assumptions and evaluation methodology for RLF failure prediction |
|
| R2-2406312 |
Discussion on RLF use case |
OPPO |
| R2-2406343 |
Simulation assumption for RLF prediction |
NEC |
| R2-2406403 |
Simulation assumptions and evaluation methodology for RLF prediction |
vivo |
| R2-2406424 |
Discussion on simulation assumption for RLF prediction |
ZTE Corporation |
| R2-2406581 |
Simulation assumptions and evaluation methodology for RLF failure prediction |
MediaTek Inc. |
| R2-2406663 |
On RLF prediction |
Apple |
| R2-2406705 |
RLF prediction simulation assumption and evaluation methodology |
Xiaomi |
| R2-2406813 |
RLF prediction and RLF prediction reporting |
Qualcomm Incorporated |
| R2-2406826 |
Discussions on simulation assumptions and EVM for RLF predictions |
NTT DOCOMO, INC. |
| R2-2406832 |
Simulation assumptions and evaluation methodology for RLF prediction |
CATT, Turkcell |
| R2-2406885 |
Discussion on RLF Prediction |
Lenovo |
| R2-2406937 |
Discussion on simulation assumptions and evaluation methodology for RLF failure prediction |
Huawei, HiSilicon |
| R2-2406976 |
Discussion on Simulation Assumption and Methodology for RLF prediction |
CMCC |
| R2-2407071 |
AI-ML based RLF/HO failure prediction |
Rakuten Mobile, Inc |
| R2-2407093 |
AI/ML based RLF predictions |
Ericsson |
| R2-2407211 |
Simulation assumptions and evaluation methodology for RLF prediction |
InterDigital Inc. |
| R2-2407289 |
Evaluation Assumptions for RLF/HO Failure Prediction |
Meta Ireland |
| R2-2407389 |
Discussion on simulation assumption for RLF prediction |
KDDI Corporation |
| R2-2407481 |
RLF Prediction Aspects |
Nokia |
| R2-2407492 |
Discussion on simulation assumptions and evaluation methodology for RLF prediction |
Samsung |
| R2-2407514 |
RLF prediction result for indirect case |
LG Electronics France |
| 8.3.4.2 |
Other aspects related to RLF/HO failure prediction |
|
| R2-2406313 |
Discussion on RLF use case |
OPPO |
| 8.4.2 |
Procedure and configuration of LP-WUS in RRC_IDLE/INACTIVE |
|
| R2-2406427 |
Discussion on LP-WUS WUR in RRC_IDLE INACTIVE |
vivo |
| R2-2406447 |
Procedure and configuration of LP-WUS for IDLE and INACTIVE mode |
ZTE Corporation, Sanechips |
| R2-2406495 |
LP-WUS procedure in RRC_IDLE INACTIVE |
NEC |
| R2-2406575 |
LP-WUS in RRC_IDLE/INACTIVE |
CATT |
| R2-2406585 |
General considerations on the procedure for RRC_IDLE_INACTIVE |
Xiaomi Communications |
| R2-2406617 |
RAN2 aspects on LP-WUS/WUR in RRC Idle/Inactive mode |
Sony |
| R2-2406730 |
Procedure and configuration of LP-WUS in RRC_IDLE/INACTIVE |
Apple |
| R2-2406753 |
Discussion on LP-WUS operation in IDLE/INACTIVE mode |
Spreadtrum Communications |
| R2-2406772 |
Discussion on procedure and configuration of LP-WUS in RRC_IDLE/INACTIVE |
OPPO |
| R2-2406787 |
Discussion on procedure and configuration of LP-WUS in RRC_IDLE/INACTIVE |
Huawei, HiSilicon |
| R2-2406802 |
Discussion on entry exit conditions for LP-WUS monitoring |
Sharp |
| R2-2406900 |
LP-WUS Operation in RRC_IDLE/INACTIVE |
China Telecom |
| R2-2406985 |
LP-WUS operation in IDLE/INACTIVE modes |
CMCC |
| R2-2407013 |
LP-WUS in IDLE and INACTIVE |
Nokia |
| R2-2407096 |
LP-WUS operation in IDLE/Inactive state |
Qualcomm Incorporated |
| R2-2407127 |
Procedure and Configuration of LP-WUS in RRC Idle/ Inactive |
Lenovo |
| R2-2407156 |
LP-WUS operation in RRC_IDLE and RRC_INACTIVE |
LG Electronics Inc. |
| R2-2407240 |
Discussion on LP-WUS operation in RRC_IDLE/INACTIVE modes |
InterDigital, Inc. |
| R2-2407310 |
Procedure and Configuration of LP-WUS in RRC Idle Inactive Mode |
Samsung |
| R2-2407357 |
Procedure of LP-WUS in RRC_IDLE and INACTIVE |
HONOR |
| R2-2407396 |
LP-WUS in Idle and Inactive |
Ericsson |
| R2-2407543 |
Discussion on Procedure and configuration in RRC_IDLE-INACTIVE |
NTT DOCOMO INC.. |
| 8.4.3 |
RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE |
|
| R2-2406285 |
RRM measurement relaxation and offloading in RRC_IDLE or RRC_INACTIVE |
Huawei, HiSilicon |
| R2-2406428 |
Discussion on RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE |
vivo |
| R2-2406448 |
RRM measurement relaxation and offloading in RRC_IDLE and RRC_INACTIVE mode |
ZTE Corporation, Sanechips |
| R2-2406496 |
LP-WUS RRM measurement |
NEC |
| R2-2406576 |
RRM Relaxation and Offloading in RRC_IDLE/INACTIVE |
CATT |
| R2-2406586 |
Discussion on RRM measurement relaxation for RRC_IDLE_INACTIVE |
Xiaomi Communications |
| R2-2406618 |
Discussion on RRM aspects for LP-WUS/WUR |
Sony |
| R2-2406731 |
RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE |
Apple |
| R2-2406739 |
Discussion on RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE mode |
China Telecom |
| R2-2406754 |
Discussion on RRM measurement relaxation and offloading in IDLE/INACTIVE mode |
Spreadtrum Communications |
| R2-2406767 |
Discussion on RRM measurement in RRC IDLE and INACTIVE |
OPPO |
| R2-2406803 |
Discussion on RRM measurement offloading and relaxation |
Sharp |
| R2-2406882 |
RRM measurement relaxation and offloading in RRC_IDLE/INACTIVE |
Lenovo |
| R2-2406970 |
Discussion on RRM measurement relaxation and offloading in RRC_IDLE INACTIVE |
CMCC |
| R2-2407014 |
RRM measurement relaxation in RRC_IDLE/INACTIVE |
Nokia |
| R2-2407098 |
LP-WUS RRM measurement relaxation and offloading |
Qualcomm Incorporated |
| R2-2407157 |
RRM relaxation and RRM offloading |
LG Electronics Inc. |
| R2-2407241 |
Discussion on RRM measurement relaxation and offloading |
InterDigital, Inc. |
| R2-2407311 |
RRM measurement relaxation and offloading in RRC Idle Inactive Mode |
Samsung |
| R2-2407397 |
LP-WUS and RRM measurements |
Ericsson |
| 8.4.4 |
Procedures for LP-WUS in RRC_CONNECTED |
|
| R2-2406429 |
Discussion on LP-WUS WUR in RRC_Connected |
vivo |
| R2-2406449 |
Procedures for LP-WUS in RRC_CONNECTED |
ZTE Corporation, Sanechips |
| R2-2406497 |
LP-WUS procedure in RRC_CONNECTED |
NEC |
| R2-2406577 |
Analysis on LP-WUS for RRC_CONNECTED Mode |
CATT |
| R2-2406587 |
Discussing on LP-WUS monitoring for RRC_Connected |
Xiaomi Communications |
| R2-2406619 |
Considerations on LP-WUS/WUR in RRC Connected mode |
Sony |
| R2-2406717 |
Discussion on LP-WUS for RRC_CONNECTED mode |
Huawei, HiSilicon |
| R2-2406732 |
Procedures for LP-WUS in RRC_CONNECTED |
Apple |
| R2-2406768 |
Discussion on LP-WUS in RRC_CONNECTED |
OPPO |
| R2-2406901 |
Discussion on LP-WUS in RRC_CONNECTED |
China Telecom |
| R2-2406978 |
Discussion on LP-WUS operation in CONNECTED mode |
CMCC |
| R2-2407097 |
LP-WUS operation in CONNECTED state |
Qualcomm Incorporated |
| R2-2407134 |
LP-WUS in RRC Connected Mode |
Lenovo |
| R2-2407242 |
Discussion on LP-WUS operation in RRC_CONNECTED mode |
InterDigital, Inc. |
| R2-2407286 |
Discussion on Procedures for UE MR PDCCH monitoring triggered by LP-WUS in RRC_CONNECTED Mode |
LG Electronics Inc. |
| R2-2407312 |
Procedures for LP-WUS in RRC Connected Mode |
Samsung |
| R2-2407358 |
Discussion on LP-WUS in RRC_CONNECTED |
HONOR |
| R2-2407398 |
LP-WUS in Connected |
Ericsson |
| R2-2407406 |
LP-WUS in RRC_CONNECTED |
Nokia |
| R2-2407512 |
Discussion on LP-WUS in RRC_CONNECTED |
NTT DOCOMO INC.. |
| 8.5.2 |
On-demand SSB SCell operation |
|
| R2-2406266 |
Discussion on On-Demand SSB |
OPPO |
| R2-2406347 |
On-demand SSB SCell Operation |
Samsung Electronics Co., Ltd |
| R2-2406425 |
Discussion on on-demand SSB |
Xiaomi |
| R2-2406444 |
On-demand SSB SCell operation in connected mode |
ZTE Corporation, Sanechips |
| R2-2406469 |
RAN2 impacts to enable on-demand SSB SCell |
Intel Corporation |
| R2-2406620 |
On-demand SSB Scell operation discussion |
Sony |
| R2-2406669 |
Discussion on RAN2 work of on-demand SSB for Scell |
Apple |
| R2-2406721 |
Discussion on on-demand SSB SCell operation |
vivo |
| R2-2406749 |
Discussion on on-demand SSB Scell operation |
Spreadtrum Communications |
| R2-2406889 |
Issues on the procedure of on-demand SSB SCell operation |
Lenovo |
| R2-2406895 |
Discussion on on-demand SSB |
China Telecom |
| R2-2406954 |
On demand SSB handling |
Nokia, Nokia Shanghai Bell |
| R2-2406979 |
Discussion on on-demand SSB |
CMCC |
| R2-2407002 |
Consideration on on-demand SSB SCell operation |
CATT |
| R2-2407039 |
Discussion on on-demand SSB for NES |
Ericsson |
| R2-2407123 |
Discussion on On-demand SSB for SCell |
NEC |
| R2-2407158 |
On-demand SSB SCell operation |
LG Electronics Inc. |
| R2-2407161 |
Discussion on On-demand SSB SCell Operation |
Qualcomm |
| R2-2407162 |
Discussion on On-demand SIB1 |
Qualcomm Incorporated |
| R2-2407185 |
On demand SSB transmission for SCell |
InterDigital |
| R2-2407271 |
Discussion on on-demand SSB SCell operation |
Fujitsu |
| R2-2407304 |
Discussion on on-demand SSB SCell operation for NES |
Huawei, HiSilicon |
| R2-2407414 |
Discussion on on-demand SSB SCell operation |
Sharp |
| 8.5.3 |
On-demand SIB1 |
|
| R2-2406346 |
On-demand SIB1 |
Samsung Electronics Co., Ltd |
| R2-2406359 |
Discussion on on-demand SIB1 |
Xiaomi |
| R2-2406445 |
Remaining issues of on-demand SIB1 in idle and inactive mode |
ZTE Corporation, Sanechips |
| R2-2406470 |
Remaining details to enable on-demand SIB1 |
Intel Corporation |
| R2-2406569 |
The procedure for the on-demand SIB1 transmission |
Google |
| R2-2406605 |
Discussion on on-demand SIB1 operation for NES |
Huawei, HiSilicon |
| R2-2406621 |
On-demand SIB1 for IDLE/INACTIVE UEs |
Sony |
| R2-2406622 |
Further study on Case 3 in on-demand SIB1 |
Sony |
| R2-2406653 |
Discussion on On-demand SIB1 for RAR |
KDDI Corporation |
| R2-2406659 |
Discussion on on-demand SIB1 transmission for network energy savings |
Fujitsu Limited |
| R2-2406670 |
Finalize study of on-demand SIB1 |
Apple Inc, BT Plc |
| R2-2406722 |
Discussion on on-demand SIB1 for RRC IDLE and INACTIVE UE |
vivo |
| R2-2406780 |
Consideration on on-demand SIB1 |
OPPO |
| R2-2406804 |
Discussion on on-demand SIB1 |
Sharp |
| R2-2406896 |
Discussion on left issues of on-demand SIB1 |
China Telecom |
| R2-2406955 |
On demand SIB1 handling |
Nokia, Nokia Shanghai Bell |
| R2-2406980 |
Discussion on on-demand SIB1 |
CMCC |
| R2-2407003 |
Consideration on on-demand SIB1 issues |
CATT |
| R2-2407041 |
Discussion on on-demand SIB1 for NES |
Ericsson |
| R2-2407042 |
Discussion on on-demand SIB1 for NES |
Rakuten Mobile, Inc |
| R2-2407043 |
Discussion on On-demand SIB1 procedure and UL WUS configuration |
NEC |
| R2-2407051 |
Detection and access of NES cells with OD-SIB1 |
Rakuten Mobile, Inc |
| R2-2407159 |
On-demand transmission of SIB1 |
LG Electronics Inc. |
| R2-2407183 |
On-demand SIB1 request and reception |
InterDigital |
| R2-2407351 |
Further discussion on on-demand SIB1 |
HONOR |
| R2-2407438 |
Remaining essential issues for study |
Lenovo |
| R2-2407455 |
Discussion on on-demand SIB1 |
NTT DOCOMO INC.. |
| R2-2407499 |
On-demand SIB1 for NES |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2407540 |
On-demand SIB1 for Idle/Inactive mode UEs |
III |
| 8.5.4 |
Adaptation of common signal/channel transmissions |
|
| R2-2406270 |
Discussion on PO confinement options |
OPPO, Samsung, ZTE, Huawei, HiSilicon, Qualcomm |
| R2-2406348 |
Adaptation of common signal channel transmissions |
Samsung Electronics Co., Ltd |
| R2-2406360 |
Discussion on common signal adaptation |
Xiaomi |
| R2-2406446 |
Further consideration on paging occasion adaptation |
ZTE Corporation, Sanechips |
| R2-2406471 |
RAN2 impacts to enable adaptation of paging and RACH in time |
Intel Corporation |
| R2-2406523 |
Discussion on paging adaptation |
ASUSTeK |
| R2-2406544 |
Adaptation of common signal or channel |
Fujitsu |
| R2-2406671 |
Further discussion on common signal transmission adaptation |
Apple |
| R2-2406723 |
Discussion on adaptation on common signal transmissions |
vivo |
| R2-2406750 |
Discussion on adaptation of common signal channel transmissions |
Spreadtrum Communications |
| R2-2406866 |
Discussion on the paging occasion adaptation for NES cell |
ITRI |
| R2-2406890 |
Paging statistics from field and PRACH adaptation |
Lenovo |
| R2-2406897 |
Discussion of adaption of paging occasions |
China Telecom |
| R2-2406956 |
Common signal aspects of NES WI |
Nokia, Nokia Shanghai Bell |
| R2-2406981 |
Discussion on adaptation of common signal channel transmissions |
CMCC |
| R2-2407004 |
Consideration on adaptation of common signalchannel transmissions |
CATT |
| R2-2407048 |
PRACH and paging adaptation |
NEC |
| R2-2407163 |
Discussion on Adaptation of Common Signal/Channel Transmissions |
Qualcomm Incorporated |
| R2-2407184 |
Time domain adaptation of common signalling and channels |
InterDigital |
| R2-2407245 |
Adaptation of common signal/channel transmissions for NES |
Ericsson |
| R2-2407305 |
Discussion on adaptation of common signals/channels transmissions |
Huawei, HiSilicon |
| R2-2407352 |
Discussion on adaptation of common channel transmissions |
HONOR |
| R2-2407440 |
Discussion on RACH adaptation |
SHARP |
| R2-2407454 |
Discussion on Adaptation of paging occasions |
NTT DOCOMO INC.. |
| R2-2407486 |
Adaptation of Common Signals and Channels for NES |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2407520 |
Discussion on common signal and channel adaptation |
LG Electronics Inc. |
| R2-2407531 |
Adaptation of common signal/channel transmissions |
III |
| R2-2407598 |
Summary of [109] |
OPPO |
| 8.6.1 |
Organizational |
|
| R2-2406244 |
Reply LS to RAN2 on security handling for inter-CU LTM in non-DC cases (S3-242400; contact: Apple) |
SA3 |
| R2-2406693 |
Important topics for resolution for Rel-19 Mob Enh WI (Rapporteur) |
Apple Inc, China Telecom |
| 8.6.2 |
Inter-CU LTM |
|
| R2-2406305 |
Discussion on inter-CU LTM |
CATT |
| R2-2406356 |
Further discussion on Inter-CU LTM |
MediaTek Inc. |
| R2-2406386 |
Discussion on inter-CU LTM |
ETRI |
| R2-2406419 |
Discussion on inter-CU LTM |
ZTE Corporation |
| R2-2406430 |
Discussion on inter-CU LTM |
vivo |
| R2-2406532 |
Discussion on open issues for inter-CU LTM |
OPPO |
| R2-2406623 |
LTM for Inter-CU |
Sony |
| R2-2406658 |
Discussion on Inter-CU LTM |
InterDigital, Inc. |
| R2-2406694 |
View on open issues in inter-CU LTM |
Apple |
| R2-2406743 |
Discussion on inter-CU LTM |
KT Corp. |
| R2-2406775 |
Discussion on Inter CU LTM |
Lekha Wireless Solutions |
| R2-2406819 |
Discussion on Inter-CU LTM |
Xiaomi |
| R2-2406820 |
Initial considerations for inter-CU LTM |
Rakuten Mobile, Inc |
| R2-2406854 |
Discussion on inter-CU LTM |
NEC |
| R2-2406863 |
Cell switch command for subsequent inter-CU LTM |
ITRI |
| R2-2406867 |
Discussion on the reference configuration for inter-CU LTM |
ITRI |
| R2-2406919 |
Important aspects regarding inter-CU LTM |
Ericsson |
| R2-2406982 |
Discussion on Inter-CU LTM |
CMCC |
| R2-2407023 |
Further detailed discussion on supporting inter-CU LTM cell switch |
Transsion Holdings |
| R2-2407033 |
Security impacts of Inter-CU LTM |
Rakuten Mobile, Inc |
| R2-2407073 |
On Inter-CU LTM Open Issues |
Nokia |
| R2-2407107 |
Radio Resource aspects for intra-CU and inter-CU LTM |
Rakuten Mobile, Inc |
| R2-2407108 |
Discussion on Inter-CU LTM |
China Telecom |
| R2-2407133 |
Fast LTM recovery in DC scenarios |
Rakuten Mobile, Inc |
| R2-2407155 |
RACH-less LTM completion in inter-CU LTM |
Rakuten Mobile, Inc |
| R2-2407201 |
Inter-CU LTM |
Huawei, HiSilicon |
| R2-2407269 |
Discussion on inter-CU LTM |
LG Electronics |
| R2-2407320 |
Discussion on subsequent inter-CU or inter-CU LTM |
Fujitsu |
| R2-2407348 |
Further discussion on inter-CU LTM |
HONOR |
| R2-2407374 |
Inter-gNB LTM with no change of RRC/PDCP anchor |
Qualcomm Incorporated, NTT DOCOMO, Vodafone, Bharti Airtel (India), Sony |
| R2-2407407 |
Discussion on issues for supporting inter-CU LTM |
Sharp |
| R2-2407421 |
Further Considerations to Support Inter-CU LTM |
Samsung |
| R2-2407439 |
Discussion on inter-CU LTM |
Kyocera |
| R2-2407441 |
Discussion on inter-CU LTM |
DENSO CORPORATION |
| R2-2407448 |
Discussion on Inter-CU LTM |
Lenovo |
| R2-2407465 |
Discussion on inter-CU LTM |
ITL |
| R2-2407478 |
RRC Modelling for Inter-CU LTM |
Nokia |
| R2-2407483 |
LTM enhancements for Inter-CU mobility |
CEWiT |
| R2-2407561 |
Initial considerations for inter-CU LTM |
Rakuten Mobile, Inc |
| R2-2407602 |
LS on security key update of inter-CU SCG LTM |
RAN2 |
| R2-2407793 |
Summary of offline discussion on DRB handling in subsequent LTM |
Samsung |
| 8.6.3 |
Measurement event evaluation |
|
| R2-2406286 |
Discussion on measurement event evaluation |
Huawei, HiSilicon |
| R2-2406287 |
Discussion on event triggered report |
Huawei, HiSilicon |
| R2-2406306 |
Measurement Event Evaluation |
CATT |
| R2-2406357 |
Discussion on measurement and signalling design |
MediaTek Inc. |
| R2-2406420 |
Discussion on measurement event evaluation |
ZTE Corporation |
| R2-2406431 |
Discussion on LTM measurement event evaluation |
vivo |
| R2-2406524 |
Discussion on beam for evaluation of LTM event-triggered reporting |
ASUSTeK |
| R2-2406533 |
Open issues for event triggered L1 measurement reporting |
OPPO |
| R2-2406545 |
Open issues of measurement event evaluation for LTM |
Fujitsu |
| R2-2406707 |
Discussion on the measurement event evaluation for LTM |
Xiaomi |
| R2-2406728 |
LTM measurement event evaluation and configuration |
Apple |
| R2-2406733 |
Measurement enhancements for LTM |
Qualcomm Incorporated |
| R2-2406756 |
Discussion on measurement event evaluation for L1 measurement event |
Spreadtrum Communications |
| R2-2406851 |
Further View on Measurement-related Enhancements for Rel-19 LTM |
Nokia |
| R2-2406886 |
L1 Measurement enhancements |
Lenovo |
| R2-2406908 |
Discussion on measurement event evaluation for LTM |
Lekha Wireless Solutions |
| R2-2406920 |
Important aspects regarding event triggered L1 measurements |
Ericsson |
| R2-2406968 |
Discussion on measurement event evaluation |
CMCC |
| R2-2407024 |
Discussion on event triggered L1 measurement configuration for LTM |
Transsion Holdings |
| R2-2407109 |
Discussion on measurement event evaluation for LTM |
China Telecom |
| R2-2407124 |
Event evaluation of L1 measurement reporting |
NEC |
| R2-2407141 |
Event triggered L1 measurement evaluation for LTM |
Interdigital, Inc. |
| R2-2407160 |
Event based L1 measurements triggered LTM candidate cell addition/release |
Rakuten Mobile, Inc |
| R2-2407195 |
Reference resource configuration for L1 measurement event |
Panasonic |
| R2-2407349 |
Discussion on measurement event evaluation |
HONOR |
| R2-2407393 |
Discussion on measurement event evaluation |
KDDI Corporation |
| R2-2407408 |
Discussion issues on related to measurement event evaluation |
Sharp |
| R2-2407422 |
Remaining Issues for Measurement Event Evaluation |
Samsung |
| R2-2407446 |
Measurement event evaluation for LTM enhancement |
Kyocera |
| R2-2407470 |
Discussion on event triggered L1 measurement |
ITL |
| R2-2407506 |
Event LTM - Event variant, new event, RS determination, configuration |
LG Electronics France |
| 8.6.4 |
Measurement reporting |
|
| R2-2406307 |
Measurement Reporting |
CATT |
| R2-2406358 |
Discussion on measurement reporting of event triggered L1 MR |
MediaTek Inc. |
| R2-2406421 |
Discussion on measurement reporting |
ZTE Corporation |
| R2-2406432 |
Discussion on event-triggered L1 measurement reporting |
vivo |
| R2-2406534 |
Discussion on the UL signalling for L1 reproting |
OPPO |
| R2-2406546 |
Open issues of measurement reporting procedure for LTM |
Fujitsu |
| R2-2406708 |
Event-based measurement reporting procedure for L1 measurement |
Xiaomi |
| R2-2406729 |
LTM event triggered measurement reporting |
Apple |
| R2-2406757 |
Discussion on measurement reporting for L1 measurement event |
Spreadtrum Communications |
| R2-2406921 |
Discussion on which layer reports the event triggered L1 measurements |
Ericsson, Honor, Huawei, InterDigital Inc., MediaTek Inc., NEC, Nokia, NTT DOCOMO, Oppo, T-Mobile USA, Vivo, ZTE corporation |
| R2-2406969 |
Discussion on measurement reporting |
CMCC |
| R2-2407025 |
Discussion on L1 measurement reporting for LTM |
Transsion Holdings |
| R2-2407110 |
Discussion on measurement reporting for LTM |
China Telecom |
| R2-2407125 |
Details of event triggered L1 measurement report |
NEC |
| R2-2407142 |
Event triggered L1 measurement reporting for LTM |
Interdigital, Inc. |
| R2-2407208 |
Event triggered reporting enhancements for LTM |
Panasonic |
| R2-2407285 |
Discussion on Event-triggered L1 measurement reporting |
NTT DOCOMO, INC. |
| R2-2407350 |
Discussion on measurement reporting |
HONOR |
| R2-2407394 |
Discussion on event triggered L1 measurement reporting |
KDDI Corporation |
| R2-2407409 |
Discussion issues on related to measurement reporting |
Sharp |
| R2-2407423 |
Support of Event Triggered L1 Measurement Reporting |
Samsung |
| R2-2407447 |
Measurement reporting procedures for LTM enhancements |
Kyocera |
| R2-2407507 |
Event LTM - Report triggering, report contents and transmission procedure |
LG Electronics France |
| 8.7.1 |
Organizational |
|
| R2-2406216 |
LS on UE assistance information (R1-2405736; contact: Nokia) |
RAN1 |
| R2-2406221 |
LS on UL PSI based PDU discarding in NR-DC (R3-243957; contact: Qualcomm) |
RAN3 |
| R2-2406222 |
Response LS on FS_XRM Ph2 (R3-243958; contact: Lenovo) |
RAN3 |
| R2-2406241 |
LS on FS_XRM Ph2 (S2-2407351; contact: vivo) |
SA2 |
| R2-2406242 |
LS Reply on FS_XRM Ph2 (S4-241370; contact: Huawei) |
SA4 |
| R2-2406395 |
XR Workplan |
Nokia, Qualcomm (Rapporteurs) |
| R2-2406396 |
XR Agreements |
Nokia, Qualcomm (Rapporteurs) |
| R2-2406397 |
SA2 Overview |
Nokia, Qualcomm (Rapporteurs) |
| R2-2406398 |
RAN3 Overview |
Nokia, Qualcomm (Rapporteurs) |
| 8.7.1.1 |
Discussion on incoming LSs |
|
| R2-2406253 |
Draft reply to RAN3 LS on UL PSI based PDU discarding in NR-DC |
Qualcomm Incorporated |
| R2-2406254 |
Discussion on reply to RAN3 LS on PSI-based PDU discard in NR-DC |
Qualcomm Incorporated, Nokia, Nokia Shanghai Bell |
| R2-2406255 |
Discussion on reply LS to SA2 on FS_XRM Ph2 |
Qualcomm Incorporated |
| R2-2406303 |
Discussion on incoming LSs |
Huawei, HiSilicon |
| R2-2406399 |
Periodicity and Time to Next Burst |
Nokia, Nokia Shanghai Bell |
| R2-2406408 |
Discussion on SA2 and RAN3 LSs for Rel-19 XR |
Xiaomi |
| R2-2406433 |
Discussion on LS from SA2 on FS_XRM Ph2 |
vivo |
| R2-2406434 |
Discussion on LS from RAN3 on UL PSI based PDU discarding in NR-DC |
vivo |
| R2-2406457 |
Discussion on LSs for XR |
ZTE Corporation, Sanechips |
| R2-2406472 |
RAN2 views and responses to LSs from SA2, RAN3 and SA4 |
Intel Corporation |
| R2-2406480 |
Discussion on XRM and UL PSI-based PDU Discard |
Sharp |
| R2-2406558 |
Discussion on SA2 and RAN3 LSs |
CATT |
| R2-2406566 |
Discussion on SA2 LS on FS_XRM Ph2 and RAN3 LS on UL PSI based PDU discarding in NR-DC |
NEC |
| R2-2406624 |
Views on LSs for SA2 and RAN3 |
Sony |
| R2-2406675 |
On Responses to SA2 and RAN3 LS for XR |
Apple |
| R2-2406781 |
Discussion on the LS from SA2 and RAN3 |
OPPO |
| R2-2406783 |
Discussion on incoming LSs |
Samsung |
| R2-2406892 |
Discussion on RAN2 Replies to LS |
Lenovo |
| R2-2406913 |
Discussion on SA2 and RAN3 LSs for XR |
LG Electronics Inc. |
| R2-2407044 |
Discussion on LSs from SA2 and RAN3 |
Ericsson |
| R2-2407216 |
Discussion on incoming LSs |
InterDigital |
| R2-2407276 |
Discussion on SA2 and RAN3 LSs on Rel-19 XR |
Meta |
| R2-2407383 |
Discussion on LS on FS_XRM Ph2 and UL PSI based PDU discarding in NR-DC |
CMCC |
| R2-2407733 |
Reply LS on FS_XRM Ph2 |
RAN2 |
| R2-2407780 |
Reply to RAN3 LS on UL PSI based PDU discarding in NR-DC |
RAN2 |
| 8.7.2 |
Multi-modality support |
|
| R2-2406302 |
Discussion on multi-modal XR |
Huawei, HiSilicon |
| R2-2406370 |
Discussion on Multi-modality for XR |
TCL |
| R2-2406435 |
Discussion on Multi-modality |
vivo |
| R2-2406463 |
Multi-modality assistance information for RAN awareness |
ZTE Corporation, Sanechips |
| R2-2406473 |
UE/RAN enhancements considering multi-modal awareness |
Intel Corporation |
| R2-2406525 |
Discussion on DRX enhancements for multi-modality |
ASUSTeK |
| R2-2406547 |
Discussions on Multi-modality XR |
Fujitsu |
| R2-2406559 |
Discussion on Multi-Modality |
CATT |
| R2-2406567 |
Potential enhancements based on multi-modal information awareness |
NEC |
| R2-2406589 |
Discussion on Multi-modality support for XR traffic |
Xiaomi Communications |
| R2-2406595 |
Enhancements for support of Multi-Modal XR applications |
Lenovo |
| R2-2406625 |
Need for MMSID and DRB mapping |
Sony |
| R2-2406662 |
Discussion on Multi-Modality |
Sharp |
| R2-2406676 |
Views on Support of Multi-Modality Services in Rel-19 XR |
Apple |
| R2-2406740 |
Discussion on XR multi-modality |
China Telecom |
| R2-2406760 |
Discussion on enhancements for XR Multi-modality |
Spreadtrum Communications |
| R2-2406782 |
Discussion on the multi-modality support |
OPPO |
| R2-2406864 |
Discussion on scheduling enhancements for multi-modal traffic |
ITRI |
| R2-2406914 |
Discussion on Multi-modal support for XR |
LG Electronics Inc. |
| R2-2406916 |
Further aspects of multi-modality support in RAN |
Samsung R&D Institute UK |
| R2-2406988 |
Further discussion on multi-modality support for XR |
CMCC |
| R2-2407045 |
Discussion on Multi-Modality |
Ericsson |
| R2-2407135 |
Multi-modality support for XR |
Google Ireland Limited |
| R2-2407213 |
Multi-modality support for XR |
InterDigital |
| R2-2407225 |
Discussion on multi-modality |
MediaTek Inc. |
| R2-2407277 |
Discussion on Multi-Modality XR |
Meta |
| R2-2407356 |
Discussion on multi-modality support |
HONOR |
| R2-2407404 |
Multi-modality support |
Nokia |
| R2-2407516 |
Primary use cases for multi-modality support in RAN |
III |
| 8.7.4 |
Scheduling enhancements |
|
| R2-2406256 |
Discussion on delay-aware scheduling |
Qualcomm Incorporated |
| R2-2406269 |
Discussion on scheduling enhancements for XR |
OPPO |
| R2-2406371 |
Discussion on delay-aware LCP enhancement |
TCL |
| R2-2406436 |
Discussion on scheduling enhancement for XR |
vivo |
| R2-2406455 |
Scheduling enhancements for XR |
ZTE Corporation, Sanechips |
| R2-2406474 |
Scheduling enhancements using delay related information |
Intel Corporation |
| R2-2406479 |
Discussion on additional priority for delay-critical data |
SHARP Corporation |
| R2-2406548 |
Discussions on enhancement of the LCP for delay-critical data |
Fujitsu |
| R2-2406560 |
Consideration on XR-specific scheduling enhancement |
CATT |
| R2-2406588 |
Discussion on scheduling enhancements of XR traffic |
Xiaomi Communications |
| R2-2406594 |
Enhanced uplink scheduling for XR |
Lenovo |
| R2-2406626 |
UL Scheduling enhancements for XR |
Sony |
| R2-2406677 |
Views on Delay-Aware Operations for Rel-19 XR |
Apple |
| R2-2406741 |
Discussion on XR scheduling enhancements |
China Telecom |
| R2-2406761 |
Discussion on XR scheduling enhancements |
Spreadtrum Communications |
| R2-2406784 |
Scheduling enhancements for Rel-19 XR |
Samsung |
| R2-2406797 |
Delay-aware scheduling enhancements |
Huawei, HiSilicon |
| R2-2406798 |
Considerations on delay-sensitive scheduling for XR |
NEC |
| R2-2406858 |
Discussion on DSR enhancement |
TCL |
| R2-2406923 |
Discussion on additional priority for delay aware LCP |
CANON Research Centre France |
| R2-2406939 |
Discussion on Delay status report |
CANON Research Centre France |
| R2-2406989 |
Further discussion on scheduling enhancement on XR |
CMCC |
| R2-2407047 |
Discussion on scheduling enhancements |
Ericsson |
| R2-2407062 |
Scheduling Enhancements for XR |
Nokia, Nokia Shanghai Bell |
| R2-2407214 |
Scheduling enhancements for XR |
InterDigital |
| R2-2407274 |
Discussion on scheduling enhancements for XR |
DENSO CORPORATION |
| R2-2407279 |
Discussion on Scheduling Enhancement for XR |
Meta |
| R2-2407354 |
Discussion on Scheduling enhancements |
HONOR |
| R2-2407384 |
Discussion on LCP enhancement for XR |
Google Ireland Limited |
| R2-2407392 |
Discussion on UL scheduling enhancements |
MediaTek Inc. |
| R2-2407460 |
Discussion on Scheduling enhancement for XR |
LG Electronics Inc. |
| R2-2407518 |
Discussion on XR scheduling enhancements |
III |
| R2-2407539 |
Discussion on UL related Scheduling Enhancements for XR |
Rakuten Mobile, Inc |
| 8.7.5 |
RLC enhancements |
|
| R2-2406257 |
Discussion on RLC enhancements |
Qualcomm Incorporated |
| R2-2406364 |
Considerations on RLC re-transmission related enhancements for XR |
KDDI Corporation |
| R2-2406367 |
Discussion on RLC re-transmission related enhancements |
OPPO |
| R2-2406400 |
RLC AM enhancements for XR |
Nokia, Nokia Shanghai Bell |
| R2-2406409 |
RLC AM retransmission enhancements |
Xiaomi |
| R2-2406437 |
Discussion on RLC enhancement for XR |
vivo |
| R2-2406443 |
RLC Enhancements for XR |
Samsung |
| R2-2406456 |
RLC enhancements for XR |
ZTE Corporation, Sanechips |
| R2-2406475 |
RLC AM enhancements for XR traffic |
Intel Corporation |
| R2-2406481 |
Analysis of RLC AM Enhancements |
Sharp |
| R2-2406549 |
Discussions on RLC enhancements |
Fujitsu |
| R2-2406561 |
Consideration on XR-specific RLC enhancement |
CATT |
| R2-2406601 |
Further Discussions on RLC AM Enhancements |
Ericsson |
| R2-2406627 |
RLC AM enhancements |
Sony |
| R2-2406678 |
Views on RLC-AM Enhancements for Rel-19 XR |
Apple |
| R2-2406734 |
Discussion on RLC AM enhancements |
Huawei, HiSilicon |
| R2-2406742 |
Discussion on RLC enhancements for XR |
China Telecom |
| R2-2406762 |
Discussion on timely RLC retransmission(s) |
Spreadtrum Communications |
| R2-2406857 |
Discussion on RLC AM enhancement |
TCL |
| R2-2406893 |
AM RLC enhancement |
Lenovo |
| R2-2406940 |
Discussion on RLC AM Enhancements |
CANON Research Centre France |
| R2-2406984 |
Discussion on the RLC Enhancements for XR |
CMCC |
| R2-2407015 |
RLC AM enhancement |
NEC |
| R2-2407215 |
RLC enhancements for XR |
InterDigital |
| R2-2407280 |
Discussion on RLC AM Enhancements for XR |
Meta |
| R2-2407355 |
Discussion on RLC enhancements |
HONOR |
| R2-2407368 |
Discussion on details of RLC enhancements for XR |
LG Electronics Inc. |
| R2-2407391 |
Discussion on RLC enhancements on small packet delay budget scenario |
MediaTek Inc. |
| R2-2407511 |
Discussions on RLC enhancements for Rel-19 XR |
Futurewei |
| 8.8.1 |
Organizational |
|
| R2-2406220 |
Reply LS on Support of Regenerative-based Satellite Access (R3-243954; contact: ZTE) |
RAN3 |
| R2-2406250 |
Introduction of LTE TN to NR NTN Mobility UE Capability |
vivo |
| R2-2406318 |
Open issue list for LTE_TN_NR_NTN_mob WI |
CATT |
| R2-2406319 |
Introduction of LTE TN to NR NTN IDLE mode mobility (Option 1) |
CATT |
| R2-2406320 |
Introduction of LTE TN to NR NTN IDLE mode mobility (Option 2) |
CATT |
| R2-2406321 |
Introduction of LTE TN to NR NTN IDLE mode mobility (Option 3) |
CATT |
| R2-2407259 |
Stage 2 Running CR for E-UTRAN to NR NTN mobility |
Samsung |
| R2-2407616 |
Stage 2 Running CR for E-UTRAN to NR NTN mobility |
Samsung |
| R2-2407617 |
Introduction of LTE TN to NR NTN IDLE mode mobility (Option 2) |
CATT |
| R2-2407618 |
Introduction of LTE TN to NR NTN Mobility UE Capability |
vivo |
| R2-2407812 |
Summary of [AT127][305][LTE_TN_NR_NTN_mob] RRC CR (CATT) |
CATT (Rapporteur) |
| 8.8.2 |
Downlink coverage enhancements |
|
| R2-2406246 |
Further Considerations on DL Coverage Enhancements |
vivo |
| R2-2406324 |
Discussion on Downlink Coverage Enhancements |
CATT |
| R2-2406490 |
Discussion on Downlink Coverage Enhancement |
Samsung |
| R2-2406550 |
Discussions on cell DTX during satellite dynamic power sharing |
Fujitsu |
| R2-2406571 |
Discussion on the DL coverage enhancement |
Google |
| R2-2406591 |
Discussion on the impact of SSB extension and cell DTXDRX for NTN |
Beijing Xiaomi Mobile Software |
| R2-2406638 |
Discussion on cell DTX |
Qualcomm Incorporated |
| R2-2406685 |
DL coverage enhancement in NTN |
Apple |
| R2-2406765 |
Discussion on DL coverage enhancement for NTN |
OPPO |
| R2-2406870 |
On beam-level DL coverage enhancement in NTN |
Lenovo |
| R2-2406894 |
Consideration on downlink coverage enhancement |
NEC Corporation |
| R2-2406902 |
Beam management of NR NTN coverage enhancement |
China Telecom |
| R2-2406952 |
Discussion on Downlink Coverage Enhancements |
CSCN |
| R2-2406993 |
Consideration on downlink coverage enhancements |
ZTE Corporation, Sanechips |
| R2-2407129 |
Idle mode considerations for downlink coverage enhancements |
Nokia, Nokia Shanghai Bell |
| R2-2407187 |
Downlink coverage enhancement for NTN |
InterDigital |
| R2-2407306 |
Discussion on DL coverage enhancements |
Huawei, HiSilicon, Turkcell |
| R2-2407345 |
Discussion on downlink coverage enhancement |
HONOR |
| R2-2407382 |
RAN2 Impact on DL coverage enhancements |
CMCC |
| R2-2407401 |
Discussion on NTN downlink coverage enhancements |
NERCDTV |
| R2-2407462 |
Discussion on downlink coverage enhancement |
LG Electronics Inc. |
| R2-2407532 |
Downlink coverage enhancement SMTC impacts |
Sequans Communications |
| R2-2407544 |
Views on DL Coverage Enhancements for NR-NTN |
Inmarsat, Viasat |
| R2-2407551 |
DL coverage enhancements |
Ericsson |
| 8.8.3 |
Uplink Capacity/Throughput Enhancement |
|
| R2-2407545 |
Views on UL Capacity Enhancements for NR-NTN |
Inmarsat, Viasat |
| 8.8.4 |
Support of Broadcast service |
|
| R2-2406247 |
Further Discussion on MBS Broadcast Provision in NTN |
vivo |
| R2-2406267 |
Discussion on MBS service in NTN system |
CAICT |
| R2-2406323 |
Discussion on support of broadcast service in NR NTN |
CATT |
| R2-2406352 |
Signalling for the support of MBS broadcast service in NTN |
ETRI |
| R2-2406491 |
Discussion on MBS Broadcast Service Area information |
Samsung |
| R2-2406551 |
Discussions on supporting broadcast intending to serve partial cell |
Fujitsu |
| R2-2406583 |
MBService area indication & geoblocking |
PANASONIC |
| R2-2406606 |
Discussion on MBS Broadcast service area signaling |
THALES |
| R2-2406628 |
Broadcast service area signaling |
Sony |
| R2-2406635 |
MBS broadcast service area information |
Qualcomm Incorporated |
| R2-2406687 |
Broadcast service support over NTN |
Apple |
| R2-2406719 |
Discussion on providing MBS service area in NTN network |
OPPO |
| R2-2406849 |
On How To Support MBS in Rel-19 NR NTN |
Nokia, Nokia Shanghai Bell |
| R2-2406865 |
Discussions on handling MRB(s) associated with intended service areas |
ITRI |
| R2-2406871 |
On broadcast service area indication in NTN |
Lenovo |
| R2-2406903 |
Signaling design of service area in NR NTN |
China Telecom |
| R2-2406958 |
Discussions on MBS in Rel-19 NTN |
TOYOTA Info Technology Center |
| R2-2406971 |
Discussion on MBS broadcast service for NR NTN |
CMCC |
| R2-2406994 |
Consideration on broadcast service ehancements |
ZTE Corporation, Sanechips |
| R2-2407049 |
Further details on intended service area for MBS and ETWS |
NEC |
| R2-2407053 |
Discussion on the support of broadcast service |
Xiaomi |
| R2-2407188 |
Support for broadcast service in NTN |
InterDigital |
| R2-2407236 |
Support for broadcast services in NR NTN |
Ericsson |
| R2-2407263 |
Considerations on MBS in NTN |
Continental Automotive |
| R2-2407307 |
Discussion on MBS broadcast over NTN |
Huawei, HiSilicon, Turkcell |
| R2-2407346 |
Discussion on the support of broadcast service |
HONOR |
| R2-2407415 |
UE behaviour for MBS related procedures |
Sharp |
| R2-2407416 |
Discussion on MBS service support for NR NTN |
Sharp |
| R2-2407418 |
Discussion on support of broadcast service in NTN |
LG Electronics France |
| R2-2407453 |
Support of broadcast service in NTN |
NERCDTV |
| R2-2407473 |
Discussion on support of broadcast service |
ITL |
| R2-2407497 |
Discussion on Support of MBS Broadcasting over NTN access |
TCL |
| R2-2407619 |
Report of [AT127][307][R19 NR NTN] service area information |
Apple |
| R2-2407622 |
LS on requirements for ETWS primary notification |
Ericsson |
| R2-2407823 |
LS on requirements for ETWS primary notification |
RAN2 |
| 8.8.5 |
Support of regenerative payload |
|
| R2-2406248 |
Discussion on RACH-less Handover with Regeneration Payload |
vivo |
| R2-2406268 |
Discussion on NTN regenerative payload |
CAICT |
| R2-2406322 |
Further discussion on regenerative payload |
CATT |
| R2-2406629 |
Satellite switch with re-sync in regenerative payload |
Sony |
| R2-2406636 |
Discussion on regenerative payload |
Qualcomm Incorporated |
| R2-2406686 |
Features support in regenerative payload architecture |
Apple |
| R2-2406744 |
Discussion on regenerative payload |
KT Corp. |
| R2-2406773 |
Discussion on satellite switch with resynch for regenerative payload |
OPPO |
| R2-2406850 |
Addressing Potential Issues for NTN over Regenerative Architecture |
Nokia, Nokia Shanghai Bell |
| R2-2406872 |
UE location verification in NTN regenerative architecture |
Lenovo |
| R2-2406904 |
Consideration of essential features supporting in regenerative payload |
China Telecom |
| R2-2406972 |
Considerations on regenerative payload |
CMCC |
| R2-2406995 |
Consideration on support of regenerative payload |
ZTE Corporation, Sanechips |
| R2-2407016 |
mobility with regenerative payload |
NEC |
| R2-2407026 |
Discussion on RACH-less handover for regenerative payload |
Transsion Holdings |
| R2-2407054 |
Discussion on the support of regenerative payload |
Xiaomi |
| R2-2407260 |
Regenerative payload for NR NTN |
Samsung |
| R2-2407264 |
Considerations on RACH-less handover for regenerative payload |
Continental Automotive |
| R2-2407308 |
Discussion on regenerative payload |
Huawei, HiSilicon, Turkcell |
| R2-2407347 |
Discussion on regenerative payload |
HONOR |
| R2-2407452 |
Discussion on time-based measurement initiation for regenerative payload |
ETRI |
| R2-2407498 |
Discussion on support of NTN regenerative payload architecture |
TCL |
| R2-2407548 |
Considerations on RACH-less handover for regenerative payload |
Continental Automotive |
| R2-2407550 |
Regenerative payload |
Ericsson |
| R2-2407623 |
LS on common TA in a regenerative payload scenario |
RAN2 |
| 8.8.6 |
LTE to NR NTN mobility |
|
| R2-2406249 |
Further Discussion on LTE TN to NR NTN Mobility |
vivo |
| R2-2406325 |
Conclusion on remaining open issues for LTE TN to NR NTN IDLE mode mobility |
CATT |
| R2-2406637 |
Idle mode mobility from LTE to NR NTN |
Qualcomm Incorporated |
| R2-2406745 |
Discussion on LTE to NR NTN mobility |
InterDigital, Inc. |
| R2-2406774 |
Discussion on LTE to NR NTN idle mode mobility |
OPPO |
| R2-2406848 |
On the Remaining Issues for E-UTRA TN to NR NTN Mobility in IDLE mode |
Nokia, Nokia Shanghai Bell |
| R2-2406873 |
NR satellite assistance information provisioning for LTE |
Lenovo |
| R2-2406905 |
Remaining issues of LTE TN to NR NTN mobility |
China Telecom |
| R2-2406973 |
Considerations on LTE to NR mobility |
CMCC |
| R2-2406996 |
Consideration on idle mode mobility between LTE TN and NR NTN |
ZTE Corporation, Sanechips |
| R2-2407017 |
LTE TN to NR NTN Idle Mode Mobility |
NEC |
| R2-2407036 |
Discussion on cell reselection from E-UTRA TN to NR NTN |
MediaTek Inc. |
| R2-2407055 |
Discussion on the cell reselection from EUTRA TN to NR NTN |
Xiaomi |
| R2-2407235 |
E-UTRAN TN to NR-NTN mobility |
Ericsson |
| R2-2407258 |
E-UTRAN TN to NR NTN mobility |
Samsung |
| R2-2407309 |
Discussion on LTE TN to NR NTN mobility |
Huawei, HiSilicon, Turkcell |
| R2-2407549 |
Views on LTE to NR-NTN Mobility |
Inmarsat, Viasat |
| 8.9.1 |
Organizational |
|
| R2-2406240 |
LS on FS_5GSAT_Ph3_ARCH conclusions (S2-2407350; contact: OPPO) |
SA2 |
| R2-2406245 |
Reply LS on FS_5GSAT_Ph3_ARCH conclusions (s3i240477; contact: Tencastle) |
SA3-LI |
| 8.9.2 |
Support of Store & Forward |
|
| R2-2406251 |
RAN2 Aspect for S&F Operation |
vivo |
| R2-2406283 |
RAN2 aspects of the Store and Forward satellite operation |
Huawei, HiSilicon, Turkcell |
| R2-2406326 |
Discussion on support of store and forward operation |
CATT |
| R2-2406526 |
Discussion on information for Store & Forward |
ASUSTeK |
| R2-2406536 |
Considerations on S&F operation from device perspective |
Telit Communications S.p.A., Novamint, Sateliot, Thales |
| R2-2406570 |
Discussion on the S&F indication |
Google |
| R2-2406639 |
Support of S&F mode operation |
Qualcomm Incorporated |
| R2-2406689 |
Support of S&F operation in IoT NTN |
Apple |
| R2-2406771 |
Discussion on Store & Forward satellite operation |
OPPO |
| R2-2406821 |
RAN2 impact on S&F mode |
MediaTek Inc. |
| R2-2406874 |
Store and Forward support in IoT NTN |
Lenovo |
| R2-2406906 |
The design of radio interface for IoT NTN Store & Forward |
China Telecom |
| R2-2406967 |
Discussion on IoT NTN Store and Forward |
CMCC |
| R2-2407018 |
Support of Store and Forward |
NEC |
| R2-2407027 |
Discussion on support of Store&Forward |
Transsion Holdings |
| R2-2407056 |
Discussion on the support of store and forward |
Xiaomi |
| R2-2407075 |
Radio-Interface Impacts for IoT-NTN SF Operations |
Nokia, Nokia Shanghai Bell |
| R2-2407152 |
Further consideration on S&F operation in IoT NTN |
ZTE Corporation, Sanechips |
| R2-2407233 |
AS Security for Store & Forward Satellite Operation |
SHARP Corporation |
| R2-2407237 |
Support for store and forward in IoT NTN |
Ericsson |
| R2-2407256 |
On SA2 progress and RAN2 aspects of Store and Forward |
Samsung |
| R2-2407353 |
Discussion on the Store and Forward satellite operation |
HONOR |
| R2-2407487 |
Considerations on S&F operation from device perspective |
Telit Communications S.p.A., Novamint, Sateliot, Thales |
| R2-2407491 |
Consideration on S&F operation |
DENSO CORPORATION |
| R2-2407537 |
Support of Store & Forward |
Sequans Communications |
| 8.9.3 |
Uplink Capacity Enhancement |
|
| R2-2406252 |
Further Discussion on EDT Enhancement for IoT-NTN |
vivo |
| R2-2406284 |
Way forward for RAN2 discussion on UL capacity enhancement |
Huawei, HiSilicon, Turkcell |
| R2-2406327 |
Consideration on the feasibility of RAN2 scope for UL capacity enhancements |
CATT |
| R2-2406592 |
Discussion on uplink capacity enhancements for IOT NTN |
Beijing Xiaomi Mobile Software |
| R2-2406593 |
Performance of Advanced Random Access Protocols |
DLR |
| R2-2406640 |
Discussion on EDT enhancements |
Qualcomm Incorporated |
| R2-2406688 |
Uplink capacity enhancement in IoT NTN |
Apple |
| R2-2406763 |
Uplink Capacity Enhancement for EDT transaction |
Spreadtrum Communications |
| R2-2406766 |
Discussion on enhanced EDT for IoT NTN |
OPPO |
| R2-2406868 |
Consideration on UL capacity enhancement for IoT-NTN |
NEC Corporation. |
| R2-2406869 |
Discussion on enhanced EDT |
MediaTek Inc. |
| R2-2406875 |
EDT for uplink capacity enhancement in NTN |
Lenovo |
| R2-2406907 |
Contention-based Msg3-EDT for IoT NTN capacity enhancement |
China Telecom |
| R2-2406974 |
Considerations on uplink capacity enhancement for IoT-NTN |
CMCC |
| R2-2407028 |
Discussion on uplink capacity enhancement |
Transsion Holdings |
| R2-2407121 |
Discussion on Contention Resolution Diversity Slotted ALOHA |
TOYOTA Info Technology Center |
| R2-2407139 |
Msg3 transmission without msg1/RAR |
Interdigital, Inc. |
| R2-2407140 |
Efficient delivery (reduced overhead) of msg4 / RRCEarlyDataComplete |
Interdigital, Inc. |
| R2-2407153 |
Further consideration on uplink capacity enhancements in IoT NTN |
ZTE Corporation, Sanechips |
| R2-2407167 |
Consideration on UL capacity enhancement for IoT NTN |
Nokia, Nokia Shanghai Bell |
| R2-2407257 |
Procedures for uplink capacity enhancements for IoT NTN |
Samsung |
| R2-2407502 |
Discussion on DSA and CRDSA Performance |
ESA, Eutelsat Group, Viasat, Inmarsat, Novamint, Echostar, Sateliot |
| R2-2407546 |
Views on UL Capacity Enhancements for IoT-NTN |
Inmarsat, Viasat |
| R2-2407552 |
UL capacity enhancements objectives for IoT NTN |
Ericsson |
| R2-2407555 |
UL capacity enhancements objectives for IoT NTN |
Ericsson |
| 8.10.2 |
MRO enhancements for Rel-18 mobility features |
|
| R2-2406527 |
Discussion on random access report for LTM |
ASUSTeK |
| R2-2406883 |
Discussion on MRO for R18 mobility |
Lenovo |
| R2-2406959 |
Discussion on MRO enhancements for R18 mobility features |
CMCC |
| R2-2407005 |
Discussion on MRO Enhancements for Mobility |
CATT |
| R2-2407029 |
MRO for Rel-18 mobility |
ZTE Corporation, Sanechips |
| R2-2407052 |
MRO enhancements for Rel-18 mobility features |
Samsung |
| R2-2407064 |
Discussion on MRO enhancement for LTM |
China Unicom |
| R2-2407065 |
Discussion on MRO enhancement for CHO with candidate SCGs |
China Unicom |
| R2-2407094 |
MRO enhancements for LTM |
NEC |
| R2-2407095 |
MRO for CHO with candidate SCG(s) |
NEC |
| R2-2407099 |
MRO enhancement for SON and MDT |
Qualcomm Incorporated |
| R2-2407105 |
MRO for R18 Mobility |
LG Electronics |
| R2-2407119 |
MRO for LTM |
Nokia |
| R2-2407120 |
MRO for CHO with candidate SCG |
Nokia |
| R2-2407122 |
Configuring UE based TA acquisition for LTM |
Rakuten Mobile, Inc |
| R2-2407191 |
SON/MDT reports for LTM |
Kyocera |
| R2-2407218 |
SON support for MRO |
Ericsson |
| R2-2407333 |
Discussion on MRO enhancements for Rel-18 mobility features |
Huawei, HiSilicon |
| R2-2407362 |
Discussion on MRO enhancement for R18 mobility features |
Sharp |
| R2-2407386 |
MRO for Rel-18 mobility features |
vivo |
| 8.10.4 |
SON/MDT for NTN |
|
| R2-2407106 |
Logging for Unchanged PCI Mobility in NTN |
LG Electronics |
| 8.10.5 |
Leftovers from Rel-18 |
|
| R2-2406884 |
Discussion on MRO for MR-DC SCG failure |
Lenovo |
| R2-2406986 |
MHI Enhancement for SCG Deactivation/Activation |
CMCC, CATT, Ericsson, ZTE, Huawei, HiSilicon |
| R2-2407006 |
Consideration on leftovers from Rel-18 SONMDT |
CATT |
| R2-2407030 |
Rel-18 leftovers for SON MDT |
ZTE Corporation, Sanechips |
| R2-2407037 |
SON/MDT enhancements for leftover topics from R18 |
Samsung |
| R2-2407100 |
SON and MDT Rel-18 leftover issues |
Qualcomm Incorporated |
| R2-2407249 |
On Rel.18 leftovers |
Ericsson |
| R2-2407334 |
Discussion on support of the Rel-18 leftovers |
Huawei, HiSilicon |
| R2-2407364 |
Discussion on R18 leftovers for SON MDT |
Sharp |
| R2-2407387 |
RACH optimization for SDT |
vivo |
| R2-2407664 |
LS on MHI enhancement solution for SCG deactivation/activation |
RAN2 |
| 8.11.1 |
Organizational |
|
| R2-2406314 |
RAN2 workplan for Rel-19 Evolution of NR duplex operation |
Huawei, HiSilicon |
| 8.11.2 |
Random access in SBFD |
|
| R2-2406342 |
Random Access for SBFD Operation |
NEC |
| R2-2406363 |
Discussion on RACH in SBFD |
Xiaomi |
| R2-2406452 |
Impacts on the random access by the evolution of duplex operation |
Huawei, HiSilicon |
| R2-2406486 |
Discussion on SBFD random access operation |
CATT |
| R2-2406630 |
SBFD configuration and supporting Random access |
Sony |
| R2-2406690 |
Framework to support RACH in SBFD |
Apple |
| R2-2406724 |
Discussion on random access in SBFD |
vivo |
| R2-2406794 |
Discussion on random access procedure in SBFD |
ZTE Corporation |
| R2-2406822 |
Random Access Aspect of SBFD |
Nokia Corporation |
| R2-2406962 |
Discussion on random access in SBFD |
CMCC |
| R2-2407078 |
Discussion on subband full duplex (SBFD) RA operation |
Ericsson |
| R2-2407143 |
Random Access in Sub-Band Full Duplex |
Google Ireland Limited |
| R2-2407192 |
Views on random access for SBFD |
Qualcomm Incorporated |
| R2-2407313 |
Random access in SBFD |
Samsung |
| R2-2407461 |
Discussion on Random Access procedure for SBFD |
LG Electronics Inc. |
| 8.11.3 |
Other aspects |
|
| R2-2406410 |
SBFD resource indication and CLI handling |
Xiaomi |
| R2-2406466 |
Other impacts by the evolution of duplex operation |
Huawei, HiSilicon |
| R2-2406487 |
Discussion on other aspects of SBFD |
CATT |
| R2-2406725 |
Discussion on other issues in SBFD |
vivo |
| R2-2406795 |
Discussion on CLI measurement in SBFD |
ZTE Corporation |
| R2-2406957 |
Other aspects of SBFD |
Nokia |
| R2-2406983 |
Discussion on SBFD related issues |
CMCC |
| R2-2407079 |
Non-RA aspects for subband full duplex (SBFD) operation |
Ericsson |
| R2-2407194 |
Other aspects of SBFD |
Qualcomm Incorporated |
| R2-2407427 |
SBFD Overall and Support of Cross Link Interference |
Samsung |
| 8.13.1 |
Organizational |
|
| R2-2407145 |
Work plan for NR sidelink multi-hop relay |
LG Electronics, InterDigital |
| R2-2407147 |
Terminologies and Scenarios for SL multihop relay |
LG Electronics Inc. |
| R2-2407378 |
Discussion on Working Assumptions for Multi-hop Relay Mechanisms |
InterDigital France R&D, SAS, LG Electronics, FirstNet, Ericsson, AT&T, Qualcomm, Samsung |
| R2-2407390 |
Discussion on Working Assumptions for Multi-hop Relay Mechanisms |
InterDigital France R&D, SAS, LG Electronics, FirstNet, Ericsson, AT&T, Qualcomm, Samsung, Sharp |
| 8.13.2 |
Relay discovery and (re)selection |
|
| R2-2406365 |
Discovery and relay (re)selection for multi-hop U2N relay |
OPPO |
| R2-2406528 |
Discussions on relay discovery for multi-hop U2N Relay |
ASUSTeK |
| R2-2406553 |
Discussion on multi-hop U2N relay discovery and relay selection |
NEC |
| R2-2406562 |
Discussion on multi-hop discovery and (re)selection |
CATT |
| R2-2406611 |
Initial considerations on relay discovery and (re)selection |
Samsung |
| R2-2406632 |
Multi-hop relay selection/re-selection |
Sony |
| R2-2406683 |
Relay discovery and selection for Multi-hop UE-to-NW Relay |
Apple |
| R2-2406695 |
Discussion on discovery and (re)selection for support of multi-hop SL Relay |
ZTE Corporation, Sanechips |
| R2-2406714 |
Discovery and relay (re)selection for multi-hop relay |
InterDigital France R&D, SAS |
| R2-2406735 |
Discussion on multi-hop relay discovery and (re)selection |
vivo |
| R2-2406887 |
Relay discovery and (re)selection in Multi-hop relay |
Lenovo |
| R2-2406898 |
Discussion on multi-hop relay discovery and reselection |
China Telecom |
| R2-2407007 |
Discussion on multi-hop U2N Relay discovery and (re)selection |
vivo |
| R2-2407035 |
discussion on discovery and relay (re)selection |
Ericsson, FirstNet, AT&T |
| R2-2407057 |
Discussion on Relay discovery and selection |
LG Electronics France |
| R2-2407101 |
Discovery and Relay (re)selection for multi-hop U2N relay |
Qualcomm Incorporated |
| R2-2407204 |
Discussion on relay discovery and (re)selection for NR sidelink multi-hop relay |
TOYOTA InfoTechnology Center |
| R2-2407205 |
Discovery and (re)selection under multihop relay |
Kyocera |
| R2-2407224 |
Discussion on Working Assumptions for Multi-hop Relay Mechanisms |
FirstNet, Ericsson, AT&T, LG Electronics, InterDigital, Qualcomm |
| R2-2407294 |
Relay discovery and (re)selection for multi-hop Relay |
Huawei, HiSilicon |
| R2-2407316 |
Relay discovery and reselection for multi-hop relay |
Nokia |
| R2-2407402 |
discussion on Relay discovery and (re)selection for multi-hop relay |
Sharp |
| 8.13.3 |
Control Plane Procedures |
|
| R2-2406366 |
Control plane procedures of multi-hop U2N relay |
OPPO |
| R2-2406494 |
Discussion on control plane procedures for multi-hop relays |
MediaTek Inc. |
| R2-2406506 |
Considerations on Control Plane of Multi-hop Relay |
NEC |
| R2-2406529 |
Discussions on the L2 Intermediate U2N Relay in multi-hop L2 U2N Relay |
ASUSTeK |
| R2-2406563 |
E2E Connection Setup and QoS Split for Multi-hop Relay |
CATT |
| R2-2406612 |
Initial considerations on CP and UP aspects for R19 multi-hop relay |
Samsung |
| R2-2406633 |
Control plane procedure for multi-hop U2N relay |
Sony |
| R2-2406684 |
Control Plane Design for Multi-hop UE-to-NW Relay |
Apple |
| R2-2406696 |
Discussion on architecture and control plane procedures for support of multi-hop SL relay |
ZTE Corporation, Sanechips |
| R2-2406713 |
Scenarios, QoS Handling, and Control Plane Procedures for Multi-hop |
InterDigital France R&D, SAS |
| R2-2406736 |
Discussion on Multi-hop Control Plane Procedures |
vivo |
| R2-2406755 |
Discussion on QoS handling for NR sidelink multi-hop relay |
Spreadtrum Communications |
| R2-2406888 |
Control plane in Multi-hop relay |
Lenovo |
| R2-2407008 |
Discussion on multi-hop U2N Relay Control Plane Procedures |
vivo |
| R2-2407034 |
discussion on control plane procedure |
Ericsson, FirstNet, AT&T |
| R2-2407058 |
Discussion on Control Plane Procedure |
LG Electronics France |
| R2-2407102 |
Control procedure for multi-hop L2 based U2N relay |
Qualcomm Incorporated |
| R2-2407111 |
Discussion on control plane procedures for NR sidelink multi-hop relay |
China Telecom |
| R2-2407206 |
Control Plane under multihop L2 U2N relaying |
Kyocera |
| R2-2407295 |
Control plane procedures for multi-hop relay |
Huawei, HiSilicon |
| R2-2407318 |
Control plane procedure for multi-hop relay |
Nokia |
| R2-2407403 |
discussion on C-plane procedure for multi-hop relay |
Sharp |
| 9.1 |
Session on V2X/SL, R19 NES and MOB |
|
| R2-2407571 |
Report from session on V2X/SL, R19 NES and MOB |
Vice Chairman (Samsung) |
| 9.2 |
Session on R18 MIMOevo, R18 MUSIM, and R19 LP-WUS |
|
| R2-2407572 |
Report from session on R18 MIMOevo, R18 MUSIM, and R19 LP-WUS |
Vice Chairman (CATT) |
| 9.3 |
Session on NR NTN and IoT NTN |
|
| R2-2407573 |
Report from session on NR NTN and IoT NTN |
Session chair (ZTE) |
| 9.4 |
Session on positioning and sidelink relay |
|
| R2-2407574 |
Report from session on positioning and sidelink relay |
Session chair (MediaTek) |
| R2-2407757 |
(reserved) |
Nathan's tdocs |
| R2-2407758 |
(reserved) |
Nathan's tdocs |
| R2-2407759 |
(reserved) |
Nathan's tdocs |
| R2-2407760 |
(reserved) |
Nathan's tdocs |
| 9.5 |
Session on R18 MBS, R18 QoE and R19 XR |
|
| R2-2407575 |
Report from session on R18 MBS, R18 QoE and R19 XR |
Session chair (Huawei) |
| 9.6 |
Session on maintenance, SON/MDT and eRedCap |
|
| R2-2407576 |
Report from session on maintenance, CovEnh, SON/MDT and eRedCap |
Session chair (Ericsson) |